RUTHVEN MCP server

• Registry nameai.ruthven/ruthvenverified in the MCP registry

The registry name sits under ruthven.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools9
• Server calls itselfruthven
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 255 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score85 of 100answers 100 · definitions 93 · context 100 · use 0 · connects 100
• Answered100% of days15 of 15 daily checks
• Median first answer612 ms
• Space in an agent's context≈ 1,751 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsA · 93 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 4 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• ruthven_get_asset

  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…

• ruthven_list_evidence

  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…

• ruthven_get_evidence

  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.

• ruthven_get_provenance

  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).

• ruthven_verify_claim

  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.

• ruthven_get_proof

  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…

• ruthven_ask

  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…

• ruthven_agent_stage_records

  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…

• ruthven_describe

  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.