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.

io.github.0xsims/rubric-mcp

NPM · @RUBRIC-PROTOCOL/MCP-SERVER · SCANNED SEP 20

Attested evidence tools for AI agents: sanctions screening, agent/wallet records, paid via x402.

0 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 787 tokens (~56/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 14% 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.0xsims/rubric-mcp server?

io.github.0xsims/rubric-mcp runs locally as an npm package, launched with npx -y @rubric-protocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @rubric-protocol/mcp-server

# add to Claude Code
claude mcp add 0xsims-rubric-mcp -- npx -y @rubric-protocol/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "0xsims-rubric-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rubric-protocol/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "0xsims-rubric-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rubric-protocol/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add 0xsims-rubric-mcp -- npx -y @rubric-protocol/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0xsims-rubric-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rubric-protocol/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add 0xsims-rubric-mcp --command npx --arg -y --arg @rubric-protocol/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  0xsims-rubric-mcp:
    command: "npx"
    args: ["-y", "@rubric-protocol/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "0xsims-rubric-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@rubric-protocol/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add 0xsims-rubric-mcp -t stdio -c npx -a -y @rubric-protocol/mcp-server
// mcp.json
{
  "mcpServers": {
    "0xsims-rubric-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rubric-protocol/mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 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.

  • 18 Sept 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 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.

  • 13 Sept 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.

  • 11 Sept 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.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@rubric-protocol/mcp-server@2.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 114 packages
Packages resolved 114
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~787 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
agent_record ~64

PAID ($0.005 USDC): unforgeable operating history for any agent attesting through Rubric - record count, first-seen, continuity, recent activity, from HCS-anchored records that cannot be backdated.

NameTypeReqDescription
agent_idstringyes

No output schema declared.

No examples provided.

attest ~70

Attest an AI decision. With RUBRIC_API_KEY: HCS-anchored on Hedera mainnet. Without: PQ-signed local Merkle leaf in ~/.rubric/local-bundles/.

NameTypeReqDescription
agent_idstring
metadataobject
payloadstringyes

No output schema declared.

No examples provided.

attested_inference ~66

PAID ($0.01 USDC): gpt-4o-mini completion plus attestation binding prompt hash, response hash, exact model version, timestamp - evidence of which model said what, when.

NameTypeReqDescription
max_tokensnumber
promptstringyes

No output schema declared.

No examples provided.

bundle_query ~50

Query attestation bundles by leaf type, agent, or time range. Requires Standard+ tier.

NameTypeReqDescription
agentIdstring
leafTypestring
limitnumber

No output schema declared.

No examples provided.

cost_estimate ~32

Estimate monthly Rubric cost from expected decision volume. No key required.

NameTypeReqDescription
decisions_per_daynumberyes

No output schema declared.

No examples provided.

framework_detect ~61

Auto-detect applicable regulatory frameworks (EU AI Act, SR 26-2, HIPAA, NIST AI RMF, etc.) from decision content. Works offline, no key required.

NameTypeReqDescription
metadataobject
payloadstringyes

No output schema declared.

No examples provided.

get_proof ~42

Generate ZK Merkle inclusion proof (Noir/Barretenberg) for an attestation. Requires API key.

NameTypeReqDescription
attestation_idstringyes

No output schema declared.

No examples provided.

hedera_fact ~59

PAID ($0.001 USDC): one attested Hedera network fact (exchange-rate, gas-fees, supply, nodes, throughput, topic-state) with the attestation ID of the served snapshot.

NameTypeReqDescription
factstringyes

No output schema declared.

No examples provided.

register_agent ~46

Register an agent and receive a free Rubric developer API key via email.

NameTypeReqDescription
agent_namestringyes
emailstringyes
use_casestring

No output schema declared.

No examples provided.

screen_entity ~112

PAID ($0.01 USDC): sanctions and export-control screening across OFAC SDN + Consolidated, UN, UK OFSI, EU, and BIS lists (76K+ entries). Returns per-list results plus a signed, Hedera-anchored attestation - audit evidence you screened, against which list versions, and what it said. Requires RUBRIC_WALLET_KEY.

NameTypeReqDescription
namestringyesentity or individual name
query_idstringoptional caller reference echoed into evidence

No output schema declared.

No examples provided.

status ~25

Federation health across US/SG/JP/CA/EU nodes + ZK node.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify ~38

Verify an attestation. Checks local store first, then federation. Merkle inclusion + HCS anchoring.

NameTypeReqDescription
attestation_idstringyes

No output schema declared.

No examples provided.

verify_audit ~57

PAID ($0.002 USDC): independent audit of a Rubric attestation - signature, HCS sequence, mirror-node confirmation - returning a signed verdict with its own attestation ID.

NameTypeReqDescription
attestation_idstringyes

No output schema declared.

No examples provided.

wallet_record ~65

PAID ($0.005 USDC): attested x402 payment history for a Base/EVM buyer wallet from an append-only settlement ledger - settlements, first/last seen, spend, services. Evidence, not opinion.

NameTypeReqDescription
addressstringyes0x wallet address

No output schema declared.

No examples provided.

Common questions

What is the io.github.0xsims/rubric-mcp server?

io.github.0xsims/rubric-mcp is listed in the public MCP registry as io.github.0xsims/rubric-mcp. Attested evidence tools for AI agents: sanctions screening, agent/wallet records, paid via x402. This page covers its npm package (@rubric-protocol/mcp-server).

Is the io.github.0xsims/rubric-mcp server safe to use?

io.github.0xsims/rubric-mcp scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.0xsims/rubric-mcp server expose?

io.github.0xsims/rubric-mcp exposes 14 tools: attest, verify, get_proof, register_agent, status, and 9 more. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.

Is the io.github.0xsims/rubric-mcp server still maintained?

io.github.0xsims/rubric-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.