rco.wefetch.ai MCP Server

by wefetch Your server? Claim it

answering

rco.wefetch.ai is answering right now. Last checked 11 min ago. It exposes 4 tools.

Every receipt wefetch issues. Anyone can verify one.

Uptime history 39 hours of history

39 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

246 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check rco.wefetch.ai every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add rco --transport http https://rco.wefetch.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://rco.wefetch.ai/mcp

~/.codex/config.toml

[mcp_servers.rco]
url = "https://rco.wefetch.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "rco": {
      "url": "https://rco.wefetch.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "rco": {
      "type": "http",
      "url": "https://rco.wefetch.ai/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

receipt

write_receipt

Issue one receipt (issuer credential required, as the credential argument or a Bearer header). subject = the barcode; market; core_version; profile_version; answer_hash; match_hash; result = verified · listed · stale · unknown with the four readings (source_authority, disagreement, freshness, authorisation); supersedes = an earlier receipt id, when this one replaces it. Never revokes.

receipts

list_receipts

List receipts, newest first, by barcode (subject), country (market) or date (since, YYYY-MM-DD); up to 500.

statement

get_statement

The signed statement for a month (YYYY-MM): receipts issued, by result, by country and by key id, the receipts that supersede earlier ones, and the chain tip.

verify

verify_receipt

Verify one receipt by id (pm_…), in public: the receipt, its hash, id, signature and chain link checked, the receipts that supersede it, and the public key it was signed under.

Endpoints

URL	Transport	State	Latency	Checked
https://rco.wefetch.ai/mcp	streamable-http	answering	206 ms	11 min ago

Alternatives to rco.wefetch.ai

same job, measured the same way

getauditor: the Auditor door

by allooloo

The auditor of an issuer and every change on the record, dated: signed and receipted (RCO-10060).

3 tools answering

Receipt — sign an agent's work, verify it offline

by ecstatica

Ed25519 receipts over work artifacts: issue and verify offline, no account, no chain, no network.

2 tools answering

Speccheck

by cloudcorprecords

Verify every spec requirement is claimed by an issue, PR, or code reference; list gaps.

268 installs/wk local only

STEMPA

by kragos

STEMPA seals one brief every AI reads the same way, with a signed receipt.

answering

Knowngood

by knowngood

Search agent-ready sites or fetch one site's report; every capability probe-verified, dated.

3 tools answering

Warrant

by s0fractal

Record an agent's decisions with reasons anyone can re-execute offline — verify recomputes them.

243 installs/wk local only

Agora

by mo-grantsmith

Find governed AI capabilities and verify signed receipts. Read-only, no account.

3 tools answering

Acta — Verifiable Agent Memory

by kylewilson04

Verifiable agent memory with signed ledger receipts — verify every write offline.

local only

rco.wefetch.ai — questions

Answers built from our own checks of this server.

What can rco.wefetch.ai do?

It exposes 4 tools, read directly from the server on our last check. Among them: get_statement, list_receipts, verify_receipt, write_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is rco.wefetch.ai working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 246 ms. The bar chart above shows every period we have measured.

How do I connect rco.wefetch.ai?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does rco.wefetch.ai need an API key?

No. rco.wefetch.ai completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is rco.wefetch.ai?

It answers our handshake in 246 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.