Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.ruthven/ruthven

REMOTE · RUTHVEN.AI

Artwork provenance and works for sale: Origin Passports, Ethereum proofs, listings with proof

Available components

+4 this week 83 Trust /100

Last scanned (3 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1584 tokens (~158/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1394 → 1584 ▼ functional
    • New tool “ruthven_for_sale” functional
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://ruthven.ai/api/ruthven/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ruthven.ai CN=YE1,O=Let's Encrypt,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA384 6a391610f9cc9558ce61946adc81eec2a18
SANs: ruthven.ai, www.ruthven.ai
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ruthven.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
ruthven.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ruthven.ai/api/ruthven/mcp Verified 200
http (plaintext) http://ruthven.ai/api/ruthven/mcp HTTPS enforced 301 https://ruthven.ai/api/ruthven/mcp
MCP tools · 10 exposed · ~1,336 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ruthven_agent_stage_records ~194

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_id, one record with its proof and the steps to check it against the chain without trusting RUTHVEN. Records are operator-declared; the root proves a record is the one recorded, not that a statement in it is true. No model is involved.

NameTypeReqDescription
collectionstringyesThe stage's collection slug, e.g. "paper-trail".
record_idstring–A recordId (0x… 32 bytes) from the list, for its proof.

No output schema declared.

No examples provided.

ruthven_ask ~114

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.

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
questionstringyes–

No output schema declared.

No examples provided.

ruthven_describe ~53

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ruthven_for_sale ~156

Which works of a collection can be bought right now on the open market (the artist's own listings and collectors' resales), as the marketplace reports them: token, ask, expiry, the listing's order hash and protocol address, and for each work its Origin Passport, its record and its proof — plus the exact steps to check the work and fill the listing from your own wallet, and what holding a work earns (a free RUTHVEN Origin Passport for an artwork you own). Without a collection, lists the collections that have a market answer. RUTHVEN values nothing, recommends nothing and is not a party to any sale.

NameTypeReqDescription
collectionstring–A collection slug, e.g. "paper-trail".

No output schema declared.

No examples provided.

ruthven_get_asset ~135

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

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
include_evidenceboolean–Include every evidence record and the evidence graph. Default false.

No output schema declared.

No examples provided.

ruthven_get_evidence ~103

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.

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
evidence_idstringyes–

No output schema declared.

No examples provided.

ruthven_get_proof ~197

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 paths that can be proved. Deterministic; no model is involved.

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
evidence_idsarray–Stable evidence ids (EVID-…).
pathsarray–Entry paths in the Passport, e.g. "identity.name" or "module.collection.copyrightOwner".

No output schema declared.

No examples provided.

ruthven_get_provenance ~103

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

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".

No output schema declared.

No examples provided.

ruthven_list_evidence ~172

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.

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
kindstring––
limitinteger––
offsetinteger––
qstring–Text to look for in the label or statement.
statusstring––
typestring––

No output schema declared.

No examples provided.

ruthven_verify_claim ~109

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.

NameTypeReqDescription
asset_idstringyesThe asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
evidence_idsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the ai.ruthven/ruthven MCP server?

ai.ruthven/ruthven is a hosted endpoint at https://ruthven.ai/api/ruthven/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ruthven.ai

# add to Claude Code
claude mcp add --transport http ai-ruthven-ruthven 'https://ruthven.ai/api/ruthven/mcp'
Common questions

What is the ai.ruthven/ruthven MCP server?

ai.ruthven/ruthven is an MCP server listed in the public MCP registry as ai.ruthven/ruthven. Artwork provenance and works for sale: Origin Passports, Ethereum proofs, listings with proof. This page covers its hosted endpoint (https://ruthven.ai/api/ruthven/mcp).

Is the ai.ruthven/ruthven MCP server safe to use?

ai.ruthven/ruthven scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ai.ruthven/ruthven MCP server expose?

ai.ruthven/ruthven exposes 10 tools: ruthven_get_asset, ruthven_list_evidence, ruthven_get_evidence, ruthven_get_provenance, ruthven_verify_claim, and 5 more. Their descriptions and schemas cost roughly 1,336 tokens of context every time the server is loaded.

Does the ai.ruthven/ruthven MCP server require authentication?

No. We connected to ai.ruthven/ruthven without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.ruthven/ruthven MCP server still maintained?

ai.ruthven/ruthven is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.