network.caper/caper-wiki

Est-ce que network.caper/caper-wiki est sûr ?

Au dernier audit MCP Hub, le serveur MCP « network.caper/caper-wiki » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 13 outils

• get_categories≈ 142 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_categories", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_challenge≈ 133 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_challenge", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_full_corpus≈ 299 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "get_full_corpus", "arguments": {"skip": 1, "tagPath": "texte", "maxChars": 1, "sizeOnly": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_manifest≈ 1608 tokens

  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.

  Paramètres, retour & exemple (19)

  Paramètres

  • to · string · optionnel
    swap: the cashtag of the caper token you buy
  • xrd · number · optionnel
    buy: $XRD to spend
  • from · string · optionnel
    swap: the cashtag of the caper token you sell
  • kind · string · requis · create-caper | buy | sell | swap | create-proposal | vote | count | trigger
    What the transaction does
  • name · string · optionnel
    create-caper: the caper's name
  • title · string · optionnel
    create-proposal: proposal title
  • votes · number · optionnel
    exit: vote tokens to burn (defaults to your whole balance)
  • tokens · number · optionnel
    sell / swap / exit: caper tokens to sell (exit: defaults to your whole balance)
  • account · string · requis
    Your account address (pays fees, receives tokens)
  • cashtag · string · optionnel
    Target caper's cashtag
  • iconUrl · string · optionnel
    create-caper: optional icon URL (defaults to a generated one)
  • infoUrl · string · optionnel
    create-caper: optional https project URL
  • sequence · array · optionnel
    vote: ranked on-chain option indexes, best first — a full permutation including the trailing "Do nothing" index
  • recipient · string · optionnel
    transfer-founder: the account that receives the founder badge
  • actionJson · string · optionnel
    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 · optionnel
    vote and every crank after it: the proposal's P-… code
  • description · string · optionnel
    create-caper / create-proposal: description text
  • originToken · string · optionnel
    create-caper: optional origin-token resource address (vampire launch)
  • withdrawAccrued · boolean · optionnel
    transfer-founder: claim the accrued founder fees to you first (default true); false leaves them to the recipient

  Exemple d'appel

  {"name": "get_manifest", "arguments": {"kind": "create-caper", "account": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_page≈ 337 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "get_page", "arguments": {"path": "texte", "slug": "texte", "blocks": true, "tagPath": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_page_history≈ 246 tokens

  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).

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "get_page_history", "arguments": {"path": "texte", "slug": "texte", "limit": 1, "tagPath": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_pages≈ 211 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "get_pages", "arguments": {"paths": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_recent_changes≈ 188 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "get_recent_changes", "arguments": {"days": 1, "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_daos≈ 237 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "list_daos", "arguments": {"limit": 1, "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_pages≈ 254 tokens

  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).

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "list_pages", "arguments": {"page": 1, "sort": "title", "tagPath": "texte", "pageSize": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• login≈ 261 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "login", "arguments": {"curve": "curve25519", "address": "texte", "challenge": "texte", "publicKey": "texte", "signature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_about≈ 288 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "save_about", "arguments": {"daoId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_wiki_page≈ 463 tokens

  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. Requires the Bearer token from the `login` tool, sent as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call.

  Paramètres, retour & exemple (8)

  Paramètres

  • html · string · optionnel
    Page body as HTML, e.g. <h2>…</h2><p>…</p>. Pass this or `blocks`.
  • slug · string · requis
    Page slug
  • daoId · string · requis
    Cashtag of the DAO whose wiki to edit
  • title · string · requis
    Page title
  • blocks · array · optionnel
    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`.
  • summary · string · optionnel
    Edit summary for the page's history
  • tagPath · string · optionnel
    Optional tag path, e.g. "updates" ("" = top level)
  • baseVersion · string · optionnel
    The `version` get_page returned for the page you edited. Omit only for a new page.

  Exemple d'appel

  {"name": "save_wiki_page", "arguments": {"slug": "texte", "daoId": "texte", "title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_wiki≈ 327 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "search_wiki", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_tx≈ 401 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • code · string · optionnel
    the cranks after the vote: the proposal's P-… code
  • kind · string · requis · create-caper | buy | sell | swap | proposal | vote | count | trigger
    What the transaction did
  • txHash · string · requis
    The committed transaction intent hash (txid_…)
  • cashtag · string · optionnel
    create-caper, exit and the founder kinds: the caper's cashtag
  • proposalId · number · optionnel
    proposal: the id from the create-proposal manifest response

  Exemple d'appel

  {"name": "submit_tx", "arguments": {"kind": "create-caper", "txHash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://caper.network/api/mcp