For AI agents

Your AI assistant can query this directly.

Assistants read structured shop data with its source and date instead of guessing from SEO pages — via the MCP server or the JSON-LD embedded in every record page.

Request — via MCP (example shape)

find_shop({
query: "headphones",
country: "PT"
})

Response (example shape)

{
"results": [{ "name": "example-shop.com",
"canonical_domain": "example-shop.com",
"country": "PT",
"category": "electronics" }],
"total_count": 1
}

Try it from your own assistant: ChatGPT Claude Perplexity Grok Mistral Asia/China AIs:

Logos indicate compatibility, not endorsement.

Full MCP documentation Discovery: /llms.txt · /.well-known/ai.txt · /.well-known/mcp.json · JSON-LD on every record

Data study: return windows and payment methods (citable, CC BY 4.0, with CSV)

Install it

Paste this into your MCP client config and restart. There is no one-click install link we can verify works everywhere today — this copy-paste config is the honest, tested path.

Claude Desktop / Cursor (mcpServers block)

{
  "mcpServers": {
    "openshopgraph": {
      "command": "npx",
      "args": ["mcp-remote", "https://api.openshopgraph.com/mcp"]
    }
  }
}

Generic MCP client (streamable-HTTP)

MCP endpoint (streamable-HTTP): https://api.openshopgraph.com/mcp
Server card (schema): https://openshopgraph.com/.well-known/mcp.json
Auth: find_shop, list_categories, get_shop, list_coupons,
  get_shop_policies and get_shipping_policy need no key. get_trust, report_code and
  report_issue need an "x-api-token" header (request one:
  info@openshopgraph.com, no self-service signup yet). Without a key they are not
  publicly listed.

Try these prompts

Once installed, ask your assistant things like:

“Use OpenShopGraph's find_shop to list shops from Germany in the category camping-hiking.”
“Look up bergzeit.de on OpenShopGraph — what does it state about shipping, and when was that last checked?”
“Compare shipping options and delivery times for bergzeit.de on OpenShopGraph.”
“List the discount codes OpenShopGraph currently shows, with the shop and each code's verification status.”

What the MCP server can do

All 9 tools, in one place — full schema at /.well-known/mcp.json or the integration guide.

find_shop: Search merchants by free text, optionally filtered by country.
list_categories: Enumerate the shop category taxonomy — call this before passing a category to find_shop.
get_shop: Fetch one merchant by id or domain (public view; the offers array is empty until merchant offers are ingested).
list_coupons: List currently visible discount codes, optionally by shop.
get_shop_policies: A shop's stated policies (return window, free return label, tracking, payment methods, buyer protection) and shipping terms; the facts in `policies` carry last-checked date and source.
get_shipping_policy: Earlier name of get_shop_policies, same answer. A shop's stated shipping terms (destinations, delivery estimate, free threshold), with last-checked date.
get_trust: Trust-relevant facts OpenShopGraph measured itself (TLS, hosting, domain age, registrar, payment methods) — individual signals with source and check date, deliberately no score.
report_code: Report whether a coupon code worked (write-only, no PII).
report_issue: Report a shop-level or data-fact issue as one fixed, documented reason (write-only, no free text) — queues a re-check, never changes delivered data directly.

All tools are read-only except report_code, which only appends an outcome (no PII) and does not immediately change what other tools return.