Home / MCP registry index / io.genesisre/proofrelay-mcp-verifier

GENESIS ProofRelay MCP Verifier

io.genesisre/proofrelay-mcp-verifier in the official MCP registry. Endpoint https://mcp.genesisre.io/mcp.

The registry describes it as: Read-only verifier for 25 ProofRelay MCP tools and non-confidential evidence bundles.

We read its 26 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http proofrelay-mcp-verifier https://mcp.genesisre.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "proofrelay-mcp-verifier": {
      "url": "https://mcp.genesisre.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"proofrelay-mcp-verifier","type":"http","url":"https://mcp.genesisre.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

proofrelay.get_verifier_status proofrelay.recommend_checkpoint proofrelay.verify_bundle proofrelay.normalize_payment_proof proofrelay.build_bundle_draft proofrelay.describe_stripe_entitlement_flow proofrelay.adapt_x402_payment_proof proofrelay.plan_replay_rejection_test proofrelay.wrap_mcp_tool_evidence proofrelay.map_openapi_operation_evidence proofrelay.generate_paid_tool_receipt proofrelay.scan_mcp_risk proofrelay.describe_cli_sdk_helper proofrelay.build_human_approval_receipt proofrelay.build_audit_pack_manifest proofrelay.summarize_agent_action_log proofrelay.review_vendor_risk_profile proofrelay.build_title_production_evidence proofrelay.build_closing_proof_pack proofrelay.review_wire_payoff_change proofrelay.map_lender_condition_evidence proofrelay.compute_readiness_signal proofrelay.adapt_agent_identity_evidence proofrelay.build_registry_entry proofrelay.issue_conformance_badge proofrelay.verify_signed_attestation

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-genesisre-proofrelay-mcp-verifier/badge.svg)](https://lazaretto.dev/mcp-registry/io-genesisre-proofrelay-mcp-verifier)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.