Home / MCP registry index / network.caper/caper-wiki
Caper Wiki
network.caper/caper-wiki in the official MCP registry.
Endpoint https://caper.network/api/mcp.
The registry describes it as: Read Caper's wiki and DAO on-chain data; launch a DAO, trade, and propose on Radix testnet.
We read its 16 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_wiki get_page get_pages list_pages get_recent_changes get_page_history get_categories get_full_corpus list_daos get_challenge login get_manifest submit_tx save_wiki_page delete_wiki_page save_about
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/network-caper-caper-wiki)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.