MCP server for Atlassian Confluence Data Center - access and manage content
Nothing to run from here
Radix Wiki is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Community-maintained knowledge base for Radix DLT — search, read, and contribute wiki pages.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http radix-wiki-mcp https://radix.wiki/api/mcp
# 2 — ask your agent for something these tools do
# search_wiki, get_page, list_pages and 9 more
Radix Wiki costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RAAll 1 server
radix1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http radix-wiki-mcp https://radix.wiki/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Keyword search across Radix Wiki titles and page text — the first call when you know what you are looking for. Returns a page of results, each with its title, URL, tagPath, slug, a matched snippet and the date it was last updated. The tagPath and slug identify the page every read tool accepts. Narrow with tagPath when a term is common; page through with page/pageSize. When you do not yet know what
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search term (matched against page titles and body text) |
| tagPath | string | no | Limit results to a tag path (e.g. "contents/tech/core-concepts") |
| page | number | no | Page number (default 1) |
| pageSize | number | no | Results per page (default 20, max 50) |
Read one page in full: its extracted text, current version number, update date and declared metadata. Takes either the whole path as one string (the url a listing returns works as-is) or the tagPath/slug pair it splits into — not a title. A wrong pair is answered with the tools that find a right one rather than an empty result. For the whole article set at once use get_full_corpus, and for a pag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | The whole path in one string, e.g. "contents/tech/core-concepts/utxo-model" — the form every listing returns as url. Use this or the tagPath/slug pair. |
| tagPath | string | no | Tag path (e.g. "contents/tech/core-concepts"). Ignored when path is set. |
| slug | string | no | Page slug (e.g. "utxo-model"). Ignored when path is set. |
Browse the wiki by tag path rather than by keyword — every page under a branch, newest first by default. Returns the same rows as search_wiki (title, URL, tagPath, slug, snippet, updatedAt) plus a pagination envelope carrying totalPages, hasMore and nextPage. Omit tagPath to walk the whole wiki; pass one from get_categories to stay inside a branch. Sort by title for an A-Z pass.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagPath | string | no | Filter by tag path prefix (e.g. "developers") |
| sort | string | no | Sort order (default "updatedAt") |
| page | number | no | Page number (default 1) |
| pageSize | number | no | Results per page (default 20, max 100) |
The wiki tag hierarchy as a tree, each node carrying its path, name, description and the page count of its whole branch. The cheapest way to orient before searching, and the only way to find a valid tagPath before create_page. Costs one call and a few kilobytes; prefer it to listing pages to find out what exists.
No parameter schema on file.
Pages edited within the last N days, newest first — what to poll when you are watching the wiki rather than reading it. Same row shape as list_pages. Look back at most 30 days and take at most 50 rows; for anything older, list_pages sorted by updatedAt.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | no | Look back N days (default 7, max 30) |
| limit | number | no | Max results (default 20, max 50) |
Every article as one plain-text document, for bulk ingestion rather than reading. PREFLIGHT FIRST: call it with sizeOnly=true for the exact character count, a token estimate and the per-branch breakdown — the whole corpus is several times a context window. Then pull it with maxChars (default 200000, max 1000000), or narrow it with tagPath to take one branch at a time. Truncation is page-aligne
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sizeOnly | boolean | no | Return sizes and breakdowns only, no document. Do this before the first real pull. |
| tagPath | string | no | Restrict to one branch and its descendants, e.g. "contents/tech". Omit for everything. |
| maxChars | number | no | Character budget for document (default 200000, max 1000000) |
| skip | number | no | Resume from this page index — pass the nextSkip from the previous truncated call (default 0) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter to one category: Governance, Protocol, Tooling, Ecosystem, or Community |
| workingGroup | string | no | Filter by working group name substring, e.g. "Treasury", "Legal", "NetOps" |
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 only. Narrow with from/to. The same rows chart at /charts and download at /api/charts/activity?format=c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | First day, YYYY-MM-DD (default: 30 days before the last stored day) |
| to | string | no | Last day, YYYY-MM-DD (default: the last stored day) |
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.
No parameter schema on file.
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 <token> header on every later create_page / edit_page call; tool arguments never carry it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| challenge | string | yes | The challenge from get_challenge |
| address | string | yes | Your account address (virtual account of the signing key; its public key must be an on-ledger owner_keys entry) |
| publicKey | string | yes | Ed25519 public key, hex |
| signature | string | yes | Signature over the ROLA message, hex |
| curve | string | yes | Signing curve (Ed25519 = "curve25519") |
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. Some paths are balance-gated (blog needs 50,000 $XRD). Earns contribution points.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagPath | string | yes | Tag path the page lives under (e.g. "contents/tech/core-concepts") |
| title | string | yes | Page title |
| content | array | yes | Array of typed blocks. Each needs a unique id (UUID) and a type. A content block carries semantic HTML in text; an infobox block carries nested blocks. Start with an infobox, hyperlink eve |
| metadata | object | no | Key-value metadata for the page, including excerpt (one sentence, ≤160 chars). Some tag paths require specific keys — the error names any that are missing. |
| slug | string | no | URL slug (derived from the title when omitted) |
| bannerImage | string | no | Banner image URL |
Edit an existing Radix Wiki page. Requires a ROLA bearer token — see https://radix.wiki/AGENTS.md. Fetch the page with get_page first and send the full revised block array; the version bump, block-level diff, and revision entry are computed server-side. Locked and author-only pages are rejected. Earns contribution points.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tagPath | string | yes | Tag path of the page to edit |
| slug | string | yes | Slug of the page to edit |
| content | array | no | The full revised block array (not a patch). Omit to change only the title or metadata. |
| title | string | no | New title |
| revisionMessage | string | no | What changed and why — shown in the page history. Always send one. |
| metadata | object | no | Replacement metadata object |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Radix Wiki or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.2.0.
3.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Radix Wiki can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.