Skip to content

Caper Wiki MCP server

network.caper/caper-wikicaper.networkstreamable-httpv2.7.0Scanned

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

17 tools: 3 can delete or cancel things, 1 do something that can't be undone, 4 change things and 9 only read.

Tools: 3 delete, 1 irreversible, 4 write, 9 read.
  • Reads private data · 3
  • Reads text others write · 6
  • Can send data out · 2
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Caper Wiki MCP server can do

The Caper Wiki MCP server is published by caper.network, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (3 tools: save_wiki_page, delete_wiki_page and save_about), do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (4 tools: get_challenge, login, get_manifest and submit_tx). 9 tools only read.

3 tools read private data (list_pages, get_page_history and get_full_corpus); 6 tools bring in text other people can write (list_pages, get_page_history, list_daos and 3 more); 2 tools can send data out of your system (get_manifest and send_feedback). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 3 findings (annotation-conflict and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 2.7.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Deletes or cancels 3Claude Code: deny
  • delete_wiki_pageDelete a page on a DAO's company-layer wiki, with its whole history and its Talk room.No findings

    Why it is in this group

    • The name "delete_wiki_page" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • save_aboutWrite the About section on a DAO's own page: what the caper is for, who runs it and where to follow it.No findings

    Why it is in this group

    • The name "save_about" says "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • save_wiki_pageCreate or edit a page on a DAO's company-layer wiki.No findings

    Why it is in this group

    • The name "save_wiki_page" says "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • send_feedbackTell the maintainers of Caper what you needed and did not find, what is wrong, or what broke.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Tell the maintainers of Caper what you needed and did not find, what is wrong, or what broke. One issue per call, in 300 characters at most. Reports are read, not published.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 4Claude Code: ask
  • get_challengeStep 1 of writing to Caper: a single-use ROLA challenge (5-minute expiry).1 finding

    Why it is in this group

    • The name "get_challenge" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "get_challenge" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_challenge" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Step 1 of writing to Caper: a single-use ROLA challenge (5-minute expiry). The response spells out the exact recipe for the message your Ed25519 key must sign. Writes are Stokenet-testnet only for now. You always sign with your OWN key — nothing here custodies anything. Takes no parameters.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • get_manifestStep 3: a ready-to-sign transaction manifest.Reads text others writeCan send data out2 findings

    Why it is in this group

    • The name "get_manifest" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Info

      The description is 3,440 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call."

      What this check looks for
    • Warn

      The server marks "get_manifest" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_manifest" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • loginStep 2: exchange the signed ROLA proof for a 12h Bearer token — the same verification the human wallet flow runs.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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; tool arguments never carry it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • submit_txStep 4: register a committed transaction by txHash.Reads text others writeNo findings

    Why it is in this group

    • The name "submit_tx" says "submit": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 9Show 9 read-only tools
  • get_categoriesThe category tree of the Caper knowledge base, the cheapest way to orient before searching.No findings

    Why it is in this group

    • The name "get_categories" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_full_corpusThe whole of the Caper knowledge base as one text document, for bulk ingestion.Reads private dataNo findings

    Why it is in this group

    • The name "get_full_corpus" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    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 100000, 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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_pageOne page of the Caper knowledge base in full: its text, version, update date and metadata.No findings

    Why it is in this group

    • The name "get_page" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_page_historyA page's revisions in the Caper knowledge base, newest first: each one's `id`, version, change type, message, date and the blocks it changed.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_page_history" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_pagesBatch read: 1 to 20 pages of the Caper knowledge base in full in one call, which is how to read search or listing results.No findings

    Why it is in this group

    • The name "get_pages" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_recent_changesPages 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.No findings

    Why it is in this group

    • The name "get_recent_changes" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_daosIndex of the DAOs on Caper: cashtag, name, description, member count, wiki URL, and that DAO's own MCP endpoint.Reads text others writeNo findings

    Why it is in this group

    • The name "list_daos" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_pagesBrowse the Caper knowledge base by tag path rather than by keyword: every page under a branch, newest first by default.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_pages" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "browse" and "branch": it reads repositories.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • search_wikiKeyword search across the Caper knowledge base: the first call when you know what you are looking for but not where it lives.No findings

    Why it is in this group

    • The name "search_wiki" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

36 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__caper-wiki__get_manifest",
      "mcp__caper-wiki__send_feedback"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (3 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://caper.network/api/mcp: tools/list returned 17 tools to an anonymous client, including save_wiki_page (destructive), delete_wiki_page (destructive), save_about (destructive), send_feedback (irreversible), get_challenge (write) and 3 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 7 to 8

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "get_challenge" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_challenge" says "get": a word for reading.

    What this check looks for
  • The server marks "get_manifest" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_manifest" says "get": a word for reading.

    What this check looks for
  • The description is 3,440 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...as an HTTP `Authorization: Bearer <token>` header on the POST carrying this call."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 3 changed.+1 added~3 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
    • Tools that change things, listed without credentials: 7 to 8
  3. Tools1 added, 1 changed.+1 added~1 changedView diff

Install

Pinned to version 2.7.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http caper-wiki https://caper.network/api/mcp
claude mcp add --transport http caper-wiki https://caper.network/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__caper-wiki__search_wiki",
      "mcp__caper-wiki__get_page",
      "mcp__caper-wiki__get_pages",
      "mcp__caper-wiki__list_pages",
      "mcp__caper-wiki__get_recent_changes",
      "mcp__caper-wiki__get_page_history",
      "mcp__caper-wiki__get_categories",
      "mcp__caper-wiki__get_full_corpus",
      "mcp__caper-wiki__list_daos"
    ],
    "ask": [
      "mcp__caper-wiki__get_challenge",
      "mcp__caper-wiki__login",
      "mcp__caper-wiki__get_manifest",
      "mcp__caper-wiki__submit_tx",
      "mcp__caper-wiki__send_feedback"
    ],
    "deny": [
      "mcp__caper-wiki__save_wiki_page",
      "mcp__caper-wiki__delete_wiki_page",
      "mcp__caper-wiki__save_about"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as caper-wiki. Review it before you use it.

Capability tags behind 8 rules
  • mcp__caper-wiki__list_pages private-data, untrusted-input
  • mcp__caper-wiki__get_page_history private-data, untrusted-input
  • mcp__caper-wiki__get_full_corpus private-data
  • mcp__caper-wiki__list_daos untrusted-input
  • mcp__caper-wiki__login untrusted-input
  • mcp__caper-wiki__get_manifest untrusted-input, outbound
  • mcp__caper-wiki__submit_tx untrusted-input
  • mcp__caper-wiki__send_feedback outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/network.caper/caper-wiki/verify?hash=feba9d1ad08e3447174aaa692ca819e38e199b7c237e8ec4b40c8ca1c7aa051a" | jq -e '.changed == false'

Pinned hash feba9d1ad08e, from Nov 8, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/network.caper/caper-wiki/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for network.caper/caper-wiki
[![Anlyon Radar](https://radar.anlyon.com/badge/network.caper/caper-wiki.svg)](https://radar.anlyon.com/servers/network.caper/caper-wiki)

Source: MCP Registry. Synced Oct 22, 2026, 08:18 UTC.

Caper Wiki MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Caper Wiki MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 8 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Caper Wiki MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: save_wiki_page, delete_wiki_page and save_about.

Can the Caper Wiki MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the Caper Wiki MCP server have?

17 tools: 3 destructive, 1 irreversible, 4 write, 9 read. save_wiki_page, delete_wiki_page, save_about, send_feedback, get_challenge, login, get_manifest, submit_tx and 9 more.

Does the Caper Wiki MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Caper Wiki MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_manifest and send_feedback.

Has the Caper Wiki MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.