Caper Wiki

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Read Caper's wiki and DAO on-chain data; launch a DAO, trade, and propose on Radix testnet.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Caper Wiki": {
      "url": "https://caper.network/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (16)

• search_wiki read-only

  Keyword search across the Caper knowledge base: the first call when you know what you are looking for but not where it lives. Matches titles and body prose, ranked in four tiers: titles starting with the term, titles containing it, literal body hits, then English full-text hits by relevance, which stem words and drop stopwords. Not semantic: one distinctive word beats a sentence. Each row carries a `path`, its size in `chars` and a snippet windowed on the match. Feed the paths to get_pages in one call rather than looping get_page. Narrow with tagPath when a term is common. Defaults: page 1, pageSize 20 (max 50); keep paging while `hasMore` is true.

  Parameters:

  • query (required) — string — Search term, matched against page titles and body text
  • page — number — 1-based page number (default 1)
  • tagPath — string — Only pages at this tag path, e.g. a path from get_categories
  • pageSize — number — Results per page (default 20, max 50)

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_page read-only

  One page of the Caper knowledge base in full: its text, version, update date and metadata. Address it by `path` ("tag/path/slug", exactly the `path` or `url` a listing returns), or by `tagPath` + `slug`; a category's own path reads its hub article. Not a title. For 2 to 20 pages call get_pages, one round trip rather than N. A miss names the nearest pages, so a wrong guess is fixed in one retry. A page's URL with `.md` appended is its markdown. With `blocks: true`, `content` is the stored block array, ids and all, beside the page `id` and its whole `metadata`: read a page this way before editing it, and send its `version` back as the edit's baseVersion.

  Parameters:

  • path — string — The page's whole path, e.g. "developers/scrypto/blueprints". Preferred over tagPath + slug.
  • slug — string — Page slug. Ignored when `path` is set.
  • blocks — boolean — Return the stored blocks rather than prose, for an edit
  • tagPath — string — Tag path only ("" for a top-level page). Ignored when `path` is set.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_pages read-only

  Batch read: 1 to 20 pages of the Caper knowledge base in full in one call, which is how to read search or listing results. Pass `paths` as the listings return them. Paths that do not exist come back in `missing` rather than failing the call, anything past 20 in `remaining`, and pages past `maxChars` (default 250000) in `omitted` with their sizes.

  Parameters:

  • paths (required) — array — Page paths, 1 to 20 per call
  • maxChars — number — Total characters across the pages returned (default 250000, max 1000000)

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• list_pages read-only

  Browse the Caper knowledge base by tag path rather than by keyword: every page under a branch, newest first by default. `tagPath` matches the branch and everything beneath it; omit it to walk the whole wiki. Sort by title for an A–Z pass. Same rows as search_wiki, with `totalPages`, `hasMore` and `nextPage`. Defaults: page 1, pageSize 20 (max 100).

  Parameters:

  • page — number — 1-based page number (default 1)
  • sort — string — Sort order (default "updatedAt", newest first)
  • tagPath — string — The branch to list, e.g. a path from get_categories. Includes its descendants.
  • pageSize — number — Results per page (default 20, max 100)

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_recent_changes read-only

  Pages of the Caper knowledge base edited within the last N days, newest first: what to poll when you are watching the wiki rather than reading it. Same rows as list_pages. Defaults: days 7 (max 30), limit 20 (max 50). `truncated: true` means the limit cut the list; raise it, or page through list_pages.

  Parameters:

  • days — number — Look back this many days (default 7, max 30)
  • limit — number — Most pages returned (default 20, max 50)

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_page_history read-only

  A page's revisions in the Caper knowledge base, newest first: each one's `id`, version, change type, message, date and the blocks it changed. Address the page as get_page does. A revision `id` is what a restore takes, where this server has one. Defaults: limit 20 (max 100).

  Parameters:

  • path — string — The page's whole path, e.g. "developers/scrypto/blueprints". Preferred over tagPath + slug.
  • slug — string — Page slug. Ignored when `path` is set.
  • limit — number — Most revisions returned (default 20, max 100)
  • tagPath — string — Tag path only ("" for a top-level page). Ignored when `path` is set.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_categories read-only

  The category tree of the Caper knowledge base, the cheapest way to orient before searching. Each node carries its `path` (a tagPath list_pages and search_wiki take), name, description, `pageCount` (pages filed at that path) and `pageCountDeep` (with every descendant). `tagPaths` lists every tag path that holds pages, including any the tree does not name.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_full_corpus read-only

  The whole of the Caper knowledge base as one text document, for bulk ingestion. Preflight first: sizeOnly=true returns the character count, a token estimate, the per-branch breakdown and the largest pages. Then pull it with `maxChars` (default 200000, max 1000000), or one branch at a time with `tagPath`. Truncation is page-aligned: `truncated`, `omittedPages` and `nextSkip` say where to resume (pass skip=nextSkip). For a handful of pages get_pages is cheaper.

  Parameters:

  • skip — number — Resume from this page index: the `nextSkip` of the previous truncated call (default 0)
  • tagPath — string — One branch and its descendants. Omit for everything.
  • maxChars — number — Character budget for `document` (default 200000, max 1000000)
  • sizeOnly — boolean — Sizes and breakdowns only, no document. Do this before the first real pull.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• list_daos read-only

  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-insensitive substring over cashtag, name and description. Defaults: limit 50 (max 200); `hasMore` says whether the cap cut the list.

  Parameters:

  • limit — number — Max DAOs returned (default 50, max 200)
  • query — string — Filter by cashtag, name or description (case-insensitive substring). Omit for all.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_challenge

  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.

  Hints: read-only no · destructive no · idempotent no · open-world no

• login

  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.

  Parameters:

  • challenge (required) — string — The challenge from get_challenge
  • address (required) — string — Your account address (virtual account of the signing key)
  • publicKey (required) — string — Ed25519 public key, hex
  • signature (required) — string — Signature over the ROLA message, hex
  • curve (required) — string — Signing curve (Ed25519 = "curve25519")

  Hints: read-only no · destructive no · idempotent no · open-world yes

• get_manifest

  Step 3: a ready-to-sign transaction manifest. Kinds: create-caper, buy, sell, swap, create-proposal, vote, count, trigger, resolve, execute, activate-upgrade, exit, withdraw-founder, transfer-founder. Per-kind parameters – create-caper: name, cashtag, description, infoUrl?, iconUrl?, originToken? (resource address, vampire launch); buy: cashtag, xrd ($XRD to spend); sell: cashtag, tokens (caper tokens to sell); swap: from, to (cashtags), tokens (of `from` to sell) – one transaction that sells `from` into $XRD and buys `to` with it, so it pays the skim on both legs; create-proposal: cashtag, title, description, action (one action object, or an array of up to 4 the voters rank against an appended "Do nothing"; each { kind: "PAYOUT" | "INVEST" | "DIVEST" | "UPGRADE" | "METADATA" | "DEBATE", … }; METADATA rewrites the token's mutable metadata via metadataDescription/metadataIconUrl/metadataInfoUrl, at least one; DEBATE is a non-executable debate position, title and description only, terminal at the tally). Creation costs the proposal fee – 1% of the largest option's $XRD-equivalent amount, at least 500 $XRD – banked to the treasury and kept on pass or fail; vote: cashtag, proposalId (the P-… code), sequence (ranked on-chain option indexes, best first, including the trailing "Do nothing" index); count: cashtag, proposalId (the P-… code) – returns `manifests`, one or a volley to send at once; trigger, resolve: cashtag, proposalId (the P-… code); execute: cashtag, proposalId (the P-… code); for an UPGRADE this is step one of two, which records the candidate in the registry and starts its timelock; activate-upgrade: cashtag, proposalId (the P-… code) – step two of an UPGRADE, valid once the registry timelock lifts; refused before then with the time it lifts; exit: cashtag, votes? and tokens? (vote tokens to burn and caper tokens to sell, each defaulting to your whole balance) – one transaction that burns the vote tokens for your share of the treasury and sells the caper tokens back to the curve; withdraw-founder: cashtag – claims every accrued founder-fee leg, $XRD and caper tokens, to the founder badge's holder; transfer-founder: cashtag, recipient (account), withdrawAccrued? (default true: claim the accrued legs to you first; false leaves them to the recipient) – deposits the founder badge with the recipient. Here create-proposal's action rides as actionJson, a JSON string – e.g. '{"kind":"PAYOUT","title":"Grant","currency":"<resource>","amount":100,"recipient":"<account>"}'. Governance is two-phase: 'vote' casts a ranked ballot (sequence = on-chain option indexes incl. the trailing Do-nothing, best first) during the voting window; once it closes, 'count' tallies it (it returns `manifests`, an array to send at once); a supermajority pass arms 'trigger', which locks the trailing TWAP as the baseline and opens the market window; after the window 'resolve' freezes the verdict (the winner stands unless the TWAP over that window is below the baseline) and 'execute' runs a ratified winner, an UPGRADE in two steps: 'execute', then 'activate-upgrade' once the registry timelock lifts. These cranks cost nothing beyond the network fee, and anyone can call them. You sign and submit the manifest yourself with your own key, then register the txHash with submit_tx. Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.

  Parameters:

  • kind (required) — string — What the transaction does
  • account (required) — string — Your account address (pays fees, receives tokens)
  • to — string — swap: the cashtag of the caper token you buy
  • xrd — number — buy: $XRD to spend
  • from — string — swap: the cashtag of the caper token you sell
  • name — string — create-caper: the caper's name
  • title — string — create-proposal: proposal title
  • votes — number — exit: vote tokens to burn (defaults to your whole balance)
  • tokens — number — sell / swap / exit: caper tokens to sell (exit: defaults to your whole balance)
  • cashtag — string — Target caper's cashtag
  • iconUrl — string — create-caper: optional icon URL (defaults to a generated one)
  • infoUrl — string — create-caper: optional https project URL
  • sequence — array — vote: ranked on-chain option indexes, best first — a full permutation including the trailing "Do nothing" index
  • recipient — string — transfer-founder: the account that receives the founder badge
  • actionJson — string — 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 ballot). Each is { kind: "PAYOUT" | "INVEST" | "DIVEST" | "UPGRADE" | "METADATA" | "DEBATE", … }. METADATA rewrites the token's mutable metadata (metadataDescription / metadataIconUrl / metadataInfoUrl – at least one). DEBATE is a non-executable position in a debate: title and description only, and winning it ends the proposal at the tally.
  • proposalId — string — vote and every crank after it: the proposal's P-… code
  • description — string — create-caper / create-proposal: description text
  • originToken — string — create-caper: optional origin-token resource address (vampire launch)
  • withdrawAccrued — boolean — transfer-founder: claim the accrued founder fees to you first (default true); false leaves them to the recipient

  Hints: read-only no · destructive no · idempotent no · open-world yes

• submit_tx

  Step 4: register a committed transaction by txHash. Kinds: create-caper, buy, sell, swap, proposal, vote, count, trigger, resolve, execute, activate-upgrade, exit, withdraw-founder, transfer-founder. 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, exit, withdraw-founder, transfer-founder: cashtag; proposal: proposalId; count, trigger, resolve, execute, activate-upgrade: code (the P-… code). Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.

  Parameters:

  • kind (required) — string — What the transaction did
  • txHash (required) — string — The committed transaction intent hash (txid_…)
  • code — string — the cranks after the vote: the proposal's P-… code
  • cashtag — string — create-caper, exit and the founder kinds: the caper's cashtag
  • proposalId — number — proposal: the id from the create-proposal manifest response

  Hints: read-only no · destructive no · idempotent yes · open-world yes

• save_wiki_page destructive

  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 `html`, one HTML string that becomes a standard content block (headings, paragraphs, lists, tables), or as `blocks`, the block tree the site's editor saves. To edit an existing page, read it with get_page and `blocks: true` on the DAO's MCP server, revise those blocks, and pass its `version` as `baseVersion`: a page someone else changed since is refused rather than overwritten. `newSlug` moves an existing page to another slug in its tag path, with its history. Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.

  Parameters:

  • daoId (required) — string — Cashtag of the DAO whose wiki to edit
  • slug (required) — string — Page slug
  • title (required) — string — Page title
  • html — string — Page body as HTML, e.g. <h2>…</h2><p>…</p>. Pass this or `blocks`.
  • blocks — array — Page body as the editor's block tree, e.g. [{ "id": "<uuid>", "type": "content", "text": "<p>…</p>" }]. Validated by the editor's own validator. Pass this or `html`.
  • newSlug — string — Moves an existing page to this slug in the same tag path. Omit to keep its slug.
  • summary — string — Edit summary for the page's history
  • tagPath — string — Optional tag path, e.g. "updates" ("" = top level)
  • baseVersion — string — The `version` get_page returned for the page you edited. Omit only for a new page.

  Hints: read-only no · destructive yes · idempotent no · open-world no

• delete_wiki_page destructive

  Delete a page on a DAO's company-layer wiki, with its whole history and its Talk room. Holders only, the same gate as save_wiki_page. Nothing restores it, so read it first with get_page if it may be wanted. Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.

  Parameters:

  • daoId (required) — string — Cashtag of the DAO whose wiki page to delete
  • slug (required) — string — Page slug
  • tagPath — string — The page's tag path, e.g. "updates" ("" = top level)

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• save_about destructive

  Write the About section on a DAO's own page: what the caper is for, who runs it and where to follow it. Holders only, the same gate as save_wiki_page. The section is replaced whole, so read the current one first: it is in the DAO's llms.txt and its MCP server's instructions. Pass the body as `html` or as `blocks`, as save_wiki_page takes them. Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.

  Parameters:

  • daoId (required) — string — Cashtag of the DAO whose About to write
  • html — string — Section body as HTML. Pass this or `blocks`.
  • blocks — array — Section body as the editor's block tree. Pass this or `html`.
  • summary — string — Edit summary for the section's history

  Hints: read-only no · destructive yes · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.