Every receipt wefetch issues. Anyone can verify one.
Connect Remote server
claude mcp add --transport http rco https://rco.wefetch.ai/mcp
{
"mcpServers": {
"rco": {
"url": "https://rco.wefetch.ai/mcp"
}
}
}
{
"servers": {
"rco": {
"type": "http",
"url": "https://rco.wefetch.ai/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://rco.wefetch.ai/mcp
Tools 4 found in our last check
write_receiptIssue 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, disagreeme…
verify_receiptVerify 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.
list_receiptsList receipts, newest first, by barcode (subject), country (market) or date (since, YYYY-MM-DD); up to 500.
get_statementThe 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.
Details
| Endpoint | https://rco.wefetch.ai/mcp (Streamable HTTP) |
| First published | 12 Nov 2026 |
| Last updated | 12 Nov 2026 |
| Registry name | ai.wefetch/rco |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
