Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Ruthven 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.
What it does
Read-only artwork provenance: Origin Passports, evidence states, Merkle proofs checkable on Ethereum
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ruthven-mcp https://ruthven.ai/api/ruthven/mcp
# 2 — ask your agent for something these tools do
# ruthven_get_asset, ruthven_list_evidence, ruthven_get_evidence and 6 more
Ruthven costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 ruthven-mcp https://ruthven.ai/api/ruthven/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
9 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.
The universal RUTHVEN asset record: identity, tokenization, provenance, source works, components, construction sequence, hashes, documents, rights, verified / contextual / inferred facts, unknowns, and counts. Claims carry evidence ids; pass include_evidence=true for the full evidence records as well (large).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
| include_evidence | boolean | no | Include every evidence record and the evidence graph. Default false. |
The evidence records behind an asset, each with a stable evidence_id, its source (document, locator, ipfs uri, gateway url, ledger claim id), a SHA-256, a verification state and freshness timestamps. Filter by status (VERIFIED, CONTEXT, INFERRED), type, kind, or a text query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
| status | string | no | — |
| type | string | no | — |
| kind | string | no | — |
| q | string | no | Text to look for in the label or statement. |
| limit | integer | no | — |
| offset | integer | no | — |
Retrieve the source record behind a stable evidence id (EVID-…) or an unknown id (UNK-…): where it was read from, its hash, its state, and how fresh it is.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
| evidence_id | string | yes | — |
Provenance and lineage: the timeline, source works, generated elements, components, the construction sequence, relationships, chain identity, tokenization, and the evidence graph (cut_from, placed_as, pinned_as, pictured_by, hash_of).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
Given the evidence ids a claim rests on, return the state the claim earns (the weakest among them), each record's hash and location, and how to check it independently of RUTHVEN. Deterministic; no model is involved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
| evidence_ids | array | yes | — |
A Merkle proof that evidence records are part of the issued Origin Passport, with the entry each rests on and the steps to check it without trusting RUTHVEN: SHA-256 over the entry, keccak256 up the proof, and the root compared with the one in the published Passport. It proves that the record contains the entry; it does not make a statement true. With neither evidence_ids nor paths, returns the pa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
| evidence_ids | array | no | Stable evidence ids (EVID-…). |
| paths | array | no | Entry paths in the Passport, e.g. "identity.name" or "module.collection.copyrightOwner". |
Ask a question about one asset. Returns structured JSON only: an answer, claims (each with a verification state and the evidence ids it rests on), unknowns, the full cited evidence records, and follow-up questions. Never a valuation; never a recommendation to act.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset_id | string | yes | The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1". |
| question | string | yes | — |
The acquisition records of a collection's AI Agents stage (ADR-010): every application as the stage's signer recorded it — the operator's signed declaration, the wallet, the ERC-8004 identity and its on-chain check, the quantity, the permission's salt and signer, the time — each hashed and a leaf of a Merkle root the collection's owner commits to the RuthvenAnchor registry on Ethereum. With record
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | The stage's collection slug, e.g. "paper-trail". |
| record_id | string | no | A recordId (0x… 32 bytes) from the list, for its proof. |
What RUTHVEN is and what an agent may do with it: the verification states, the permission model (READ and ANALYSE only), the asset types (live and placeholder), and the JSON API endpoints.
No parameter schema on file.
- 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 Ruthven or to call it, at any volume.
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: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. 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 1.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Ruthven can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.