Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
Caper Wiki is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Caper's wiki and DAO on-chain data; launch a DAO, trade, and propose on Radix testnet.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http caper-wiki-mcp https://caper.network/api/mcp
# 2 — ask your agent for something these tools do
# search_wiki, get_page, get_pages and 10 more
Caper Wiki costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CAAll 1 server
caper1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http caper-wiki-mcp https://caper.network/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Keyword search across the Caper knowledge base – the first call when you know what you are looking for but not where it lives. Matches page titles and body prose. A distinctive keyword is still the best query, but a whole question now works too: if the literal text is not found anywhere, it falls back to English full-text matching, which stems words and drops stopwords. NOT semantic – it reduces y
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search term. One distinctive word or short phrase beats a sentence. |
| page | number | no | 1-based page number (default 1) |
| pageSize | number | no | Results per page (default 20, max 50) |
Full text of ONE page in the Caper knowledge base. Address it by path ("dao-governance/concepts/voting/quadratic-voting" – exactly the path field the listing tools return), or by tagPath + slug. Use this only for a single known page: for 2 to 20 pages call get_pages instead, which is one round trip rather than N. Pass the path, not a page title. A miss returns near-match slugs so a wrong g
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | Full page path, e.g. "governance/voting". Preferred over tagPath+slug. |
| tagPath | string | no | Tag path only, e.g. "governance" ("" for a top-level page). Ignored when path is set. |
| slug | string | no | Page slug, e.g. "voting". Ignored when path is set. |
Batch read: full text of 1 to 20 pages in the Caper knowledge base in a single call. This is how you read search or listing results – calling get_page in a loop is the main way to waste round trips against this server. Pass paths exactly as the listing tools return them. Paths that do not exist come back in missing instead of failing the call, and anything past the 20-path cap comes back in `r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| paths | array | yes | Page paths, e.g. ["economics/token-valuation", "desci/desci-funding"]. 1-20 per call. |
| maxChars | number | no | Total character budget across returned pages (default 250000, max 1000000) |
Enumerate pages in the Caper knowledge base, newest first, optionally under one tag path. Use it to walk a branch you have already located (via get_categories, or the tagPath on a search hit); use search_wiki when you are hunting a keyword. tagPath matches the branch and everything beneath it – "daos" also returns "daos/dexs/...". Omit it to list the whole scope. Defaults: sort "updatedAt", pa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagPath | string | no | Branch to list, e.g. "daos" or "dao-governance/concepts". Prefix match, includes descendants. |
| sort | string | no | Sort order (default "updatedAt", newest first) |
| page | number | no | 1-based page number (default 1) |
| pageSize | number | no | Results per page (default 20, max 100) |
Pages in the Caper knowledge base edited within the last N days, newest first – for "what changed?", not for finding a topic (search_wiki) or reading a branch (list_pages). Defaults: days 7 (max 30), limit 20 (max 50). truncated: true means the limit cut the list, not that the window is exhausted – raise limit, or page through list_pages sorted by updatedAt. Returns summaries only; feed the `p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | no | Look back this many days (default 7, max 30) |
| limit | number | no | Max pages returned (default 20, max 50) |
Curated taxonomy of the Caper knowledge base with page counts – call this FIRST when you are orienting rather than searching. Each node returns path (a tagPath you can hand straight to list_pages), pageCount (pages sitting directly at that path) and pageCountDeep (including every descendant), so you can tell an empty heading from a populated branch before spending a call. Takes no parameters
No parameter schema on file.
The whole Caper knowledge base as one text document, for bulk ingestion. PREFLIGHT FIRST: call it with sizeOnly=true to get the exact character count, a token estimate, the per-branch breakdown and the largest pages – the corpus is big enough to swamp a context window and one operational page exceeds 500 KB on its own. Then pull it with maxChars (default 200000, max 1000000), or narrow it with `
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sizeOnly | boolean | no | Return sizes and breakdowns only, no document. Do this before the first real pull. |
| tagPath | string | no | Restrict to one branch and its descendants, e.g. "desci". Omit for everything. |
| maxChars | number | no | Character budget for document (default 200000, max 1000000) |
| skip | number | no | Resume from this page index – pass the nextSkip from the previous truncated call (default 0) |
Index of the DAOs on Caper: cashtag, name, description, member count, wiki URL, and that DAO's own MCP endpoint. Use it to resolve a name to a cashtag, then POST JSON-RPC to the returned mcpEndpoint to reach its get_ledger (treasury balances, proposal/trade/execution timeline, executed grants, inter-DAO funding) – this knowledge-base server deliberately has no ledger tool. query is a case-inse
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Filter by cashtag, name or description (case-insensitive substring). Omit for all. |
| limit | number | no | Max DAOs returned (default 50, max 200) |
Step 1 of writing to Caper: a single-use ROLA challenge (5-minute expiry). The response includes the exact recipe for the message your Ed25519 key must sign. Writes are Stokenet-testnet only for now, and you always sign with your OWN key – nothing here custodies anything. Takes no parameters.
No parameter schema on file.
Step 2: exchange the signed ROLA proof for a 12h Bearer token – the same verification the human wallet flow runs. Send the returned token as an HTTP Authorization: Bearer <token> header on every later tool call; MCP arguments never carry it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| challenge | string | yes | The challenge from get_challenge |
| address | string | yes | Your account address (virtual account of the signing key) |
| publicKey | string | yes | Ed25519 public key, hex |
| signature | string | yes | Signature over the ROLA message, hex |
| curve | string | yes | Signing curve (Ed25519 = "curve25519") |
Step 3: a ready-to-sign transaction manifest. Kinds: create-caper, buy, sell, create-proposal, vote, trigger. Per-kind parameters: create-caper needs name + cashtag + description (infoUrl/iconUrl/originToken optional); buy needs cashtag + xrd; sell needs cashtag + tokens; create-proposal needs cashtag + title + description + actionJson (one action object, or an ARRAY of up to 4 for a ranked ballot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | What the transaction does |
| account | string | yes | Your account address (pays fees, receives tokens) |
| cashtag | string | no | Target caper's cashtag |
| name | string | no | create-caper: the caper's name |
| description | string | no | create-caper / create-proposal: description text |
| infoUrl | string | no | create-caper: optional https project URL |
| iconUrl | string | no | create-caper: optional icon URL (defaults to a generated one) |
| originToken | string | no | create-caper: optional origin-token resource address (vampire launch) |
| xrd | number | no | buy: $XRD to spend |
| tokens | number | no | sell: caper tokens to sell |
| title | string | no | create-proposal: proposal title |
| actionJson | string | no | create-proposal: JSON for the action(s) — either ONE object, or an ARRAY of up to 4 that the voters rank against each other (a "Do nothing" option is always appended, so 4 actions make a 5-option ball |
Step 4: register a committed transaction by txHash. Kinds: create-caper, buy, sell, proposal, vote, trigger. The server verifies before mirroring anything: receipts are re-read on-ledger (forged or foreign txHashes are refused, replays are idempotent). Context per kind: create-caper takes cashtag; proposal takes proposalId. Requires the Bearer token from the login tool, sent as an HTTP `Authoriz
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | What the transaction did |
| txHash | string | yes | The committed transaction intent hash (txid_…) |
| cashtag | string | no | create-caper: the cashtag, so the response can confirm the row |
| proposalId | number | no | proposal: the id from the create-proposal manifest response |
Create or edit a page on a DAO's company-layer wiki. Holders only – any amount of the DAO's token, its vote token or its founder badge. Pass the body as one HTML string; it becomes a standard content block (headings, paragraphs, lists, tables). Requires the Bearer token from the login tool, sent as an HTTP Authorization: Bearer <token> header on the POST carrying this call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| daoId | string | yes | Cashtag of the DAO whose wiki to edit |
| tagPath | string | no | Optional tag path, e.g. "updates" ("" = top level) |
| slug | string | yes | Page slug |
| title | string | yes | Page title |
| html | string | yes | Page body as HTML, e.g. <h2>…</h2><p>…</p> |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Caper Wiki or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.5.0.
2.5.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Caper Wiki can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.