matchfetch MCP

An MCP server that converts natural language product descriptions or merchant offer lines into verified barcodes (GTINs) with confidence scores. It returns a single barcode, candidate list, or unknown status, supporting AI agents in grocery shopping and checkout verification by matching inputs against a verified product record.

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.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by wefetch

MCP endpoint (Streamable HTTP)

https://matchfetch.ai/mcp

Vendor documentation

What its tools do

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

Can change data (1)

match_product

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

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 11:25 PM UTC
Passed Official MCP Registry namespace is tied to matchfetch.ai · Nov 6, 2026, 11:15 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 11:15 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Verify product matches before checkout
Convert shopper phrases to barcodes
Retrieve candidate products for ambiguous queries
Check product verification status

Source and maintenance

Vendor evidenceRegistry 0.1.0

mcp-registry: ai.matchfetch/matchfetch@0.1.0 Project website

Protocol and capabilities

Server: matchfetch 0.1.7
MCP protocol negotiated in check: 2025-11-25
Tools: 1 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.

Words in, barcode out, with how sure. Give a shopper's phrase or a merchant's offer line and a country; get back one barcode with a confidence, or the candidates when it is ambiguous (never a guess), or unknown. Every result carries four verification readings (source authority, disagreement, freshness and authorisation) and one result: verified, listed, stale or unknown. Price and stock are never verified from the record: they are read live, or unknown.

Tools

1 advertised

match_product — Match Product

Advertised by the server during the last successful anonymous check.

Open-world

match_product input schema

{
  "type": "object",
  "required": [
    "words",
    "country"
  ],
  "properties": {
    "kind": {
      "type": "string",
      "default": "phrase"
    },
    "words": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "issue_receipt": {
      "type": "boolean",
      "default": false
    }
  }
}

match_product output schema

{
  "type": "object"
}

match_product annotations

{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-07: 1 of 1 checks answered

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: 1724 ms
95th percentile latency: 1724 ms

Maintenance history

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

Nov 6, 2026, 11:25 PM UTC · probe · passed · 1724 ms · metadata changed · 1 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 matchfetch-mcp https://matchfetch.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 matchfetch-mcp --url https://matchfetch.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable matchfetch-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "matchfetch-mcp": {
      "url": "https://matchfetch.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "matchfetch-mcp": {
      "type": "streamableHttp",
      "url": "https://matchfetch.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start matchfetch-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "matchfetch-mcp": {
      "type": "http",
      "url": "https://matchfetch.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 matchfetch-mcp https://matchfetch.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://matchfetch.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": {
    "matchfetch-mcp": {
      "serverUrl": "https://matchfetch.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like matchfetch 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,506

Do you run matchfetch 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