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

PYPI · RUBRIC_MCP_SERVER

Attest agent decisions and verify records on a public ledger. Evidence, not just data.

Available components

0 this week 57 Trust /100

Last scanned (17 hours ago)

Scores higher than 56% of PyPI servers

Category Security

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency6
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1027 tokens (~73/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "relay_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • 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
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.

  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 28 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 26 0
    • Stability: pass → 0.97 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 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 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed pypi/rubric_mcp_server@2.5.0

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,027 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
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.

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.

check_counterparty ~109

Get an attested OFAC/sanctions + on-chain risk screening for a Base address before transacting with it. The verdict is Hedera-anchored and citable as proof of diligence. Paid x402 service ($0.01 USDC); returns the exact payment challenge so a wallet-capable agent can obtain the live signed result.

NameTypeReqDescription
addressstringyes–
paymentstring–Signed x402 payment proof. Omit on the first call to receive the payment challenge.

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.

explain_rubric ~53

What Rubric is and why it matters: the difference between logs you control (testimony) and anchored records (evidence). Returns the trust model, how to verify independently, and pricing. No key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

framework_detect ~61

Auto-detect applicable regulatory frameworks (EU AI Act, SR 11-7, 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.

notarize ~112

Notarize any JSON record: prove it existed, unaltered, at a point in time. Returns a PROOF FILE the caller must keep - the chain stores a commitment, never the record. Paid x402 ($0.005 USDC) or with an API key. Proves existence and integrity, NOT that the record is true.

NameTypeReqDescription
labelstring––
paymentstring–Signed x402 payment proof. Omit to receive the payment challenge.
recordobjectyes–

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.

relay_pay ~151

Pay any x402 endpoint through Rubric and receive a signed, Hedera-anchored receipt of what was actually delivered: request hash, response hash, byte count, status, settlement reference. The provider is paid directly by you and Rubric never holds or submits your funds. Use this instead of calling an endpoint directly when you need provable evidence of what you received, not just the response. Free during preview, no key required.

NameTypeReqDescription
bodyobject––
methodstring–HTTP method, default GET
paymentstring–Signed x402 payment. Omit to receive the target's challenge.
urlstringyesAbsolute URL of the x402 endpoint to pay

No output schema declared.

No examples provided.

screen_name ~146

Screen a person or entity name against six sanctions and export-control lists: OFAC SDN and Consolidated (with alternate spellings), UN Security Council, UK OFSI, EU, and BIS Denied Persons. Fuzzy matching with the full rule, list versions, and per-hit edit distance disclosed in every response. Matches are CANDIDATES requiring human adjudication, not determinations. Paid x402 service ($0.01 USDC); returns the payment challenge so a wallet-capable agent can obtain the attested result.

NameTypeReqDescription
namestringyes–
paymentstring–Signed x402 payment proof. Omit on the first call to receive the payment challenge.

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_record ~92

Verify a notarization. Two independent checks: does the record hash match the proof file (offline), and is the attestation anchored on Hedera consensus (online). Always free, no key, no payment - a proof only the issuer can check is not a proof.

NameTypeReqDescription
proofobjectyesThe proof file returned by notarize
recordobject–Optional. The record to check against the proof.

No output schema declared.

No examples provided.

Install

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

io.github.0xsims/rubric-mcp-server runs locally as a PyPI package, launched with uvx rubric_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.

pypi · rubric_mcp_server

# add to Claude Code
claude mcp add 0xsims-rubric-mcp-server -- uvx rubric_mcp_server
Common questions

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

io.github.0xsims/rubric-mcp-server is listed in the public MCP registry as io.github.0xsims/rubric-mcp-server. Attest agent decisions and verify records on a public ledger. Evidence, not just data. This page covers its PyPI package (rubric_mcp_server).

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

io.github.0xsims/rubric-mcp-server scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 server expose?

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

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

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

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

io.github.0xsims/rubric-mcp-server declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.