agent-verified-relay

Viridis Verified wraps any MCP server with tamper-evident delivery receipts.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Register Service: Register a third-party MCP server (https, public FQDN only) under Viridis Verified. Returns a content-addressed service_id; idempotent on (url, provider). fee_minor is the per-verifi
  • Call Verified: Relay a tools/call to a registered MCP service and notarize the exchange: request hash + response hash + outcome land in a tamper-evident receipt chain. Idempotent on call_id (a replay
  • Get Receipt: Fetch a single delivery receipt by id.

What data it sees

Do you need an account

No: the server works without sign-in

Viridis Verified wraps any MCP server with tamper-evident delivery receipts. Relay a tools/call through the gateway and get a hash-chained receipt (request hash, response hash, outcome, latency) — idempotent, dispute-ready evidence, metered per call. Prove what an agent's tool call actually returned; audit a disputed agent-to-agent transaction. Composes with Viridis surety bonds, arbitration, and reputation. 10 free calls/day, then $0.02/call.

How to connect

How to connect agent-verified-relay to Claude

The server address to paste into Claude settings:

https://agent-verified-relay--hartjustin6.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect agent-verified-relay to ChatGPT

The server address to paste into ChatGPT settings:

https://agent-verified-relay--hartjustin6.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect agent-verified-relay to Cursor

The server address to paste into Cursor settings:

https://agent-verified-relay--hartjustin6.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (7)

Raw names from tools/list. Only developers need these.

register_serviceRegister a third-party MCP server (https, public FQDN only) under Viridis Verified. Returns a content-addressed service_id; idempotent on (url, provider). fee_minor is the per-verified-call fee in cents.
call_verifiedRelay a tools/call to a registered MCP service and notarize the exchange: request hash + response hash + outcome land in a tamper-evident receipt chain. Idempotent on call_id (a replay returns the original receipt and cached result — the downstream is never double-called). Failures are receipted evidence, not silence.
get_receiptFetch a single delivery receipt by id.
verify_receiptsRecompute a service's full receipt hash chain and fee ledger. Any party can audit Viridis Verified from receipts alone.
list_servicesList registered services with call/fee counters.
service_statsCall counts, error counts, and accrued fees for one service.
describe_agentFleet-standard self-description.