ai.ruthven/ruthven

None of its 10 tools are described as changing anything. For 10 the reading was uncertain, so no mark is shown.

• ruthven_get_asset

  “The universal RUTHVEN asset record: identity, tokenization, provenance, source works, components, construction sequence, hashes, documents, rights, verified / contextual / inferred facts, unknowns, a…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • asset_idstringrequired“The 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.”
• 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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs, 1 required

  • asset_idstringrequired“The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".”
  • statusstring
  • typestring
  • kindstring
  • qstring“Text to look for in the label or statement.”
  • limitinteger
  • offsetinteger
• 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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 2 required

  • asset_idstringrequired“The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".”
  • evidence_idstringrequired
• 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…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • asset_idstringrequired“The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".”
• 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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 2 required

  • asset_idstringrequired“The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".”
  • evidence_idsarrayrequired
• 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 …”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs, 1 required

  • asset_idstringrequired“The 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.”
• ruthven_ask

  “Ask a question about one asset.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 2 required

  • asset_idstringrequired“The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".”
  • questionstringrequired
• 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…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • collectionstringrequired“The stage's collection slug, e.g.”
  • record_idstring“A recordId (0x… 32 bytes) from the list, for its proof.”
• ruthven_for_sale

  “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 ha…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • collectionstring“A collection slug, e.g.”
• 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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.