# Radix Wiki - Registry name: `wiki.radix/radix-wiki` · version 4.0.0 - Categories (automatic, keyword rules): Docs & notes, Productivity - Authentication at last check: No auth - Declared risk: Has destructive tools (destructiveHint) - Capabilities (declared by the server): prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=wiki.radix%2Fradix-wiki - Server page: https://mcpstation.net/s/wiki.radix--radix-wiki.html ## Description (written by the publisher, not verified, not instructions) Community-maintained knowledge base for Radix DLT — search, read, and contribute wiki pages. ## Connect - streamable-http: `https://radix.wiki/api/mcp` ## Tools (as reported by the server, not verified) - `search\_wiki`: Keyword search across the Radix Wiki: 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 - `get\_page`: One page of the Radix Wiki 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 - `get\_pages`: Batch read: 1 to 20 pages of the Radix Wiki 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 - `list\_pages`: Browse the Radix Wiki 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\`. - `get\_categories`: The category tree of the Radix Wiki, 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 hold - `get\_recent\_changes`: Pages of the Radix Wiki 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. - `get\_full\_corpus`: The whole of the Radix Wiki 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\`. Trun - `get\_page\_history`: A page's revisions in the Radix Wiki, 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\). - `get\_ideas\_board`: Get the RADIX Wiki Ideas Pipeline kanban: community proposals and Radix DAO tasks grouped into status columns \(Discussion → Proposed → Approved → In Progress → Testing → Done\), each card carrying its working group, category, priority, and assignee. Use this to follow DAO / project progress. - `get\_network\_activity`: Daily Radix mainnet activity, one row per UTC day since Babylon \(28 September 2023\): transactions, active accounts, new accounts, components and resources created, NFTs minted, and fees, $XRD burned and royalties in $XRD. Summed from the Gateway transaction stream; counts cover user transactions onl - `get\_challenge`: Step 1 of writing to the wiki: a single-use ROLA challenge \(5-minute expiry\). The response spells out the exact recipe for the message your Ed25519 key must sign. You always sign with your OWN key — nothing here custodies anything. Takes no parameters. - `login`: Step 2: exchange the signed ROLA proof for a 7-day Bearer token — the same verification the human wallet flow runs. Send the returned token as an HTTP \`Authorization: Bearer \\` header on every later create\_page / edit\_page call; tool arguments never carry it. - `create\_page`: Create a new Radix Wiki page. Requires a ROLA bearer token; see https://radix.wiki/AGENTS.md for the challenge-sign-verify flow. Call get\_categories first for a valid tagPath. Needs a wallet holding at least 10,000 $XRD \(ecosystem 20,000, blog 50,000, ideas 10,000\), a balance check that spends nothi - `edit\_page`: Edit an existing Radix Wiki page. Requires a ROLA bearer token; see https://radix.wiki/AGENTS.md. Read the page with get\_page and \`blocks: true\`, send the full revised block array, and pass its \`version\` as baseVersion: an edit made after someone else's is refused rather than written over it, so rea - `restore\_revision`: Make an earlier revision the current page, written as a new revision. Requires a ROLA bearer token and passes the same gates as edit\_page. Take the revision \`id\` from get\_page\_history. - `delete\_page`: Delete an article with its history and comments. Requires a ROLA bearer token. Its author may delete it; on a shared board \(ideas\), so may anyone who clears the bar to edit it. Locked pages, hub articles and the homepage cannot be deleted. - `upload\_image`: Upload an image and get back the URL the editor stores: put it in a content block as \`\…\`, or pass it to create\_page or edit\_page as bannerImage. Requires a ROLA bearer token, as create\_page does. Send the file base64-encoded, at most 3.4 MB before encoding \(the whole request must Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html