# ai.ruthven/ruthven (remote · ruthven.ai)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ruthven.ai`: 83/100 (this document), [markdown](https://verifymcp.io/servers/ai-ruthven-ruthven/api-ruthven-mcp.md), [page](https://verifymcp.io/servers/ai-ruthven-ruthven/api-ruthven-mcp)

## Channel facts

- Endpoint: `https://ruthven.ai/api/ruthven/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http ai-ruthven-ruthven 'https://ruthven.ai/api/ruthven/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-ruthven-ruthven": {
      "url": "https://ruthven.ai/api/ruthven/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-ruthven-ruthven": {
      "type": "http",
      "url": "https://ruthven.ai/api/ruthven/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-ruthven-ruthven]
url = "https://ruthven.ai/api/ruthven/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-ruthven-ruthven": {
      "type": "remote",
      "url": "https://ruthven.ai/api/ruthven/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-ruthven-ruthven --url 'https://ruthven.ai/api/ruthven/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-ruthven-ruthven:
    url: "https://ruthven.ai/api/ruthven/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-ruthven-ruthven": {
      "Transport": "http",
      "Url": "https://ruthven.ai/api/ruthven/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-ruthven-ruthven -t streamable-http -u 'https://ruthven.ai/api/ruthven/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-ruthven-ruthven": {
      "type": "http",
      "url": "https://ruthven.ai/api/ruthven/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +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.

### 2026-11-03 (score 82, +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.

### 2026-11-01 (score 81, +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.

### 2026-10-30 (score 80, +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.

### 2026-10-27 (score 79, +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.

### 2026-10-25 (score 78, +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.

### 2026-10-23 (score 77, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1394 → 1584
- [functional] New tool “ruthven_for_sale”

### 2026-10-21 (score 76, +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.

## MCP tools (10)

### `ruthven_get_asset` (~135 tokens)

Get asset record

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

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
- `include_evidence` (boolean): Include every evidence record and the evidence graph. Default false.

### `ruthven_list_evidence` (~172 tokens)

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, INFERRED), type, kind, or a text query.

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
- `kind` (string)
- `limit` (integer)
- `offset` (integer)
- `q` (string): Text to look for in the label or statement.
- `status` (string)
- `type` (string)

### `ruthven_get_evidence` (~103 tokens)

Get one evidence record

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.

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
- `evidence_id` (string, required)

### `ruthven_get_provenance` (~103 tokens)

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

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".

### `ruthven_verify_claim` (~109 tokens)

Verify a 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.

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
- `evidence_ids` (array, required)

### `ruthven_get_proof` (~197 tokens)

Prove a claim

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.

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
- `evidence_ids` (array): Stable evidence ids (EVID-…).
- `paths` (array): Entry paths in the Passport, e.g. "identity.name" or "module.collection.copyrightOwner".

### `ruthven_ask` (~114 tokens)

Ask RUTHVEN

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.

Input parameters:

- `asset_id` (string, required): The asset: "PT-0001", a RUTHVEN ID such as "RUTHVEN-PT-0000001", or a work number such as "1".
- `question` (string, required)

### `ruthven_agent_stage_records` (~194 tokens)

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

Input parameters:

- `collection` (string, required): The stage's collection slug, e.g. "paper-trail".
- `record_id` (string): A recordId (0x… 32 bytes) from the list, for its proof.

### `ruthven_for_sale` (~156 tokens)

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

Input parameters:

- `collection` (string): A collection slug, e.g. "paper-trail".

### `ruthven_describe` (~53 tokens)

Describe RUTHVEN

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-ruthven-ruthven/api-ruthven-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-07: 69

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

## Links

- Remote endpoint: https://ruthven.ai/api/ruthven/mcp
- Repository: https://github.com/RUTHVEN19/ruthven-world
- Website: https://ruthven.ai/developers/
- Changelog RSS feed: https://verifymcp.io/servers/ai-ruthven-ruthven/api-ruthven-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-ruthven-ruthven/api-ruthven-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-ruthven-ruthven/api-ruthven-mcp