Koskamo

wefetch MCP

An MCP server for verifying product barcodes against a signed receipt chain, listing receipts, and generating statements. It allows AI agents to confirm that a purchase was verified under specific rules, providing cryptographic proof of product matches for auditing and compliance.

Visit wefetch

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

wefetch MCP logo, by wefetchVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by wefetch
MCP endpoint (Streamable HTTP)
https://rco.wefetch.ai/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (3)

Can change data (1)

4 of 4 have a description · 4 of 4 declare behavior hints · 0 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to wefetch.ai ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify a product barcode against the issuer keyring
  • List recent verified receipts
  • Generate a signed statement for a transaction
  • Check receipt validity for AI agents

Source and maintenance

Vendor evidenceRegistry 0.1.0
mcp-registry: ai.wefetch/rco@0.1.0Project website

Protocol and capabilities

Server
rco-wefetch 0.1.6
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {},
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "subscribe": false,
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

The receipt door. Every receipt wefetch issues lives here, and anyone can verify one. A receipt is the evidence that a product match was verified: the barcode, the country whose profile applied, the core and profile versions, when, the hashes of the record and the match, the result and its four readings, chained and signed. Verify, list and read statements in public; writing needs the issuer credential. A receipt is never revoked; a later one supersedes it.

Tools

4 advertised

write_receipt — Write Receipt
Advertised by the server during the last successful anonymous check.

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.

write_receipt input schema
{
  "type": "object",
  "required": [
    "subject",
    "market",
    "core_version",
    "profile_version",
    "answer_hash",
    "match_hash",
    "result",
    "source_authority",
    "disagreement",
    "freshness",
    "authorisation"
  ],
  "properties": {
    "market": {
      "type": "string"
    },
    "result": {
      "type": "string"
    },
    "subject": {
      "type": "string"
    },
    "freshness": {
      "type": "string"
    },
    "credential": {
      "type": "string",
      "default": ""
    },
    "match_hash": {
      "type": "string"
    },
    "supersedes": {
      "type": "string",
      "default": ""
    },
    "answer_hash": {
      "type": "string"
    },
    "verified_at": {
      "type": "string",
      "default": ""
    },
    "core_version": {
      "type": "string"
    },
    "disagreement": {
      "type": "string"
    },
    "authorisation": {
      "type": "string"
    },
    "profile_version": {
      "type": "string"
    },
    "source_authority": {
      "type": "string"
    }
  }
}
write_receipt output schema
{
  "type": "object"
}
write_receipt annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
verify_receipt — Verify Receipt
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

verify_receipt input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}
verify_receipt output schema
{
  "type": "object"
}
verify_receipt annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
list_receipts — List Receipts
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

list_receipts input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50
    },
    "since": {
      "type": "string",
      "default": ""
    },
    "market": {
      "type": "string",
      "default": ""
    },
    "subject": {
      "type": "string",
      "default": ""
    }
  }
}
list_receipts output schema
{
  "type": "object"
}
list_receipts annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_statement — Get Statement
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_statement input schema
{
  "type": "object",
  "properties": {
    "month": {
      "type": "string",
      "default": ""
    }
  }
}
get_statement output schema
{
  "type": "object"
}
get_statement annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1249 ms
95th percentile latency
1249 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1249 ms · metadata changed · 4 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http wefetch-mcp https://rco.wefetch.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add wefetch-mcp --url https://rco.wefetch.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable wefetch-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "wefetch-mcp": {
      "url": "https://rco.wefetch.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "wefetch-mcp": {
      "type": "streamableHttp",
      "url": "https://rco.wefetch.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start wefetch-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "wefetch-mcp": {
      "type": "http",
      "url": "https://rco.wefetch.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http wefetch-mcp https://rco.wefetch.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://rco.wefetch.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "wefetch-mcp": {
      "serverUrl": "https://rco.wefetch.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like wefetch MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,638

Do you run wefetch MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing