ruthven
Server Details
Artwork provenance and works for sale: Origin Passports, Ethereum proofs, listings with proof
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- RUTHVEN19/ruthven-world
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Most tools target clearly distinct resources or operations: evidence listing vs. retrieval, proof generation vs. claim verification, marketplace listings vs. asset records. The main overlap is between get_asset and get_provenance, since both return provenance, components, construction sequence, and tokenization information, and ruthless_ask can subsume some lookup-style questions. These are distinguishable by emphasis, but an agent may hesitate between get_asset and get_provenance.
All names share the ruthven_ prefix and consistent snake_case, which aids readability. However, the action convention is mixed: get_*, list_*, and verify_* coexist with bare verbs (ask, describe), a prepositional phrase (for_sale), and a noun phrase (agent_stage_records). This is readable but not a predictable verb_noun pattern throughout.
Ten tools is well within the appropriate range for a read-only asset verification and provenance server. Each tool covers a distinct part of the domain: overview, asset record, provenance, evidence listing and retrieval, proofs, claim verification, Q&A, marketplace listings, and agent-stage records. No tool appears clearly redundant enough to remove.
The evidence, proof, verification, provenance, and marketplace-listing surface is fairly thorough for a read-only verification API. However, there is no general list/search tool for assets or collections, so an agent must already know an asset id; for_sale can list some collections but only those with market answers. This is a notable discovery gap that could cause dead ends.
Available Tools
10 toolsruthven_agent_stage_recordsAgent Stage recordsARead-onlyIdempotentInspect
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.
Inputs: collection (required), record_id.
ruthven_askAsk RUTHVENARead-onlyIdempotentInspect
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.
Inputs: asset_id (required), question (required).
ruthven_describeDescribe RUTHVENARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
ruthven_for_saleWorks for saleARead-onlyIdempotentInspect
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.
Inputs: collection.
ruthven_get_assetGet asset recordBRead-onlyIdempotentInspect
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).
Inputs: asset_id (required), include_evidence.
ruthven_get_evidenceGet one evidence recordARead-onlyIdempotentInspect
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.
Inputs: asset_id (required), evidence_id (required).
ruthven_get_proofProve a claimARead-onlyIdempotentInspect
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.
Inputs: asset_id (required), paths, evidence_ids.
ruthven_get_provenanceGet provenanceCRead-onlyIdempotentInspect
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).
Inputs: asset_id (required).
ruthven_list_evidenceList evidenceBRead-onlyIdempotentInspect
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.
Inputs: asset_id (required), q, kind, type, +3 more.
ruthven_verify_claimVerify a claimARead-onlyIdempotentInspect
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.
Inputs: asset_id (required), evidence_ids (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AI-native art catalogue. Catalogue works, parse provenance, and generate signed RAIs.
Original art from galleries and artists: search, details, delivered prices and checkout links.
Mine, mint and verify 8004 NONCE proof-of-work art on Ethereum L1.
Browse, verify and buy Twelve Permissions NFTs on XRP Ledger. Every claim is checkable.
Related MCP Servers
- AlicenseAqualityBmaintenanceOTrust issues cryptographic PDRs (Provenance Data Records) — proving a digital artifact existed at a specific time. $0.01 per proof. Blockchain-anchored. Publicly verifiable.451MIT

markovian-mcpofficial
AlicenseAqualityCmaintenanceBitcoin-anchored provenance for AI outputs; enables stamping, verifying, and tracing outputs with offline-verifiable canonical roots.3Apache 2.0- AlicenseCqualityAmaintenanceMCP services for agent security preflight, source scanning, injection screening, proof-of-work policy rehearsal, carbon accounting, climate disclosure and regulatory monitoring. Use each hosted endpoint in the README. Inspect a free quote before buyer-authorized x402/USDC payment. Includes free trust and settlement tools. Maxwell rehearsal does not activate runtime protection.220Apache 2.0

EVIDIQ Notary MCPofficial
AlicenseNot gradedqualityBmaintenanceCryptographic receipt layer for AI inferences. Enables notarization and verification of AI outputs with on-chain proofs via x402 payment.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.