Skip to content

OpenShopGraph MCP server

com.openshopgraph/mcpopenshopgraph.comstreamable-httpv0.1.3Scanned

Source-dated facts on online shops for AI agents and buyers: returns, shipping, payment, trust.

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the OpenShopGraph MCP server can do

The OpenShopGraph MCP server is published by openshopgraph.com, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (find_shop).

The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • find_shopLook up an online shop the way a user asks about it: by name ("zalando"), domain or pasted URL ("https://www.otto.de/"), a question about a shop ("is zalando legit", "rücksendung o…Reads text others write1 finding

    Why it is in this group

    • The name "find_shop" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The description is 3,157 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...uery` (AND, not OR); `query: ""` browses a category without a name/domain filter."

      What this check looks for
    Description, as the server wrote it
    Look up an online shop the way a user asks about it: by name ("zalando"), domain or pasted URL ("https://www.otto.de/"), a question about a shop ("is zalando legit", "rücksendung otto", "does bergzeit ship to austria"), a misspelled name ("zalandoo") or a shop category in English or German ("electronics", "möbel"). It identifies the shop; it does not answer the question itself: the facts on returns, shipping, payment methods and trust are available through separate per-shop lookups by the found domain. Find online shops by name, domain fragment, country (ISO 3166-1 alpha-2, e.g. "DE") or exact category slug. Each result is a public shop profile (name, canonical domain, country, category); the source-dated facts on returns, shipping and payment methods are available through a separate per-shop policy lookup. Not a product or price search. Returns the public shop view only; shops still under internal review are not returned. `results` carries at most `limit` entries (default 50, max 100); `total_count` is the full match count before that cap and `truncated` is true when more results exist beyond the page (`offset`, default 0, selects the page). Multi-word queries are matched conjunctively: every word must be evidenced on a shop (name, domain or category). `ignored_terms` lists the words that matched nothing anywhere in the corpus and were therefore dropped to avoid an empty answer; a non-empty `ignored_terms` means the results answer a narrower question than the one asked. `match_quality` states how well the query was evidenced: "full" (every word found as a name/domain/category fragment; this is evidence of a fragment, not of relevance; results are ordered by match stage in name/domain: exact, then prefix, then word start, then substring, with category-only matches after them, ties by stable id), "partial" (some words are in `ignored_terms`; the results answer a narrower question), "none" (no match), "corrected" (the query as typed matched nothing, but a shop name or domain within typo distance exists: `results` and `total_count` are the matches for `corrected_query`, e.g. "zalandoo" -> "zalando", not for the query as typed). Question and intent words ("is", "legit", "return policy", "rücksendung", a delivery country such as "austria") and pasted URLs are reduced to the shop name or domain before matching; the dropped words are listed in `generic_terms_ignored`, and a delivery country is not a filter (`country` is where the shop is based). German category words like "schuhe" or "möbel" are matched against the English category slugs. For "partial", "none" and "corrected", `suggestions` carries hints: `categories` (known category slugs) and `shops` (domains within typo distance, e.g. "bergzeitt" -> bergzeit.de); both are empty for "full". `category_truncated` is true when category resolution hit its internal cap and the match set is a subset. `category` accepts only a slug from the shop category taxonomy; an unrecognized slug is rejected with an error and does not yield a silent empty `results`. `category` is additive to `query` (AND, not OR); `query: ""` browses a category without a name/domain filter.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Find an online shop
  • get_shipping_policyWhat a shop STATES about its own shipping: which destinations it names, the delivery time it claims, and any free-shipping threshold, plus the date that statement was last checked …No findings

    Why it is in this group

    • The name "get_shipping_policy" says "get": a word for reading.
    Description, as the server wrote it
    What a shop STATES about its own shipping: which destinations it names, the delivery time it claims, and any free-shipping threshold, plus the date that statement was last checked and where it was read (policy_page or structured_data). This is a shop-level statement, NOT an offer and NOT a quote: it carries no carrier and no shipping price, because OpenShopGraph does not hold that data. The optional country (ISO 3166-1 alpha-2, e.g. "DE") adds a ships_to verdict derived from the stated destination list; "unknown" is a real answer there and means the statement does not settle it. When nothing has been collected for a shop, the reply says so explicitly (collected:false): a gap in the data, not a statement that the shop does not ship. The checked-at date marks how current the merchant's claim is.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get shipping policy
  • get_shopGet the public profile of one online shop by domain or id (name, canonical domain, country, category) and how many of its policy facts are sourced (`fields_belegt`); the facts on r…No findings

    Why it is in this group

    • The name "get_shop" says "get": a word for reading.
    Description, as the server wrote it
    Get the public profile of one online shop by domain or id (name, canonical domain, country, category) and how many of its policy facts are sourced (`fields_belegt`); the facts on returns, shipping and payment methods are available through the separate policy lookup. Public view. Answers "shop not found" for shops still under internal review, identical to a genuinely unknown domain, so reviewers cannot be distinguished from typos. The offers array is present for schema stability and is empty for shops without ingested merchant offers. `fields_belegt` ("n/m") counts how many of the shop's policy facts carry a checked, sourced value, out of the m policy facts tracked per shop.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get shop facts
  • get_shop_policiesWhat a shop STATES about its own policies, each fact with the date it was last checked and where it was read: return window in days (returns_days), free return label, tracking offe…No findings

    Why it is in this group

    • The name "get_shop_policies" says "get": a word for reading.
    Description, as the server wrote it
    What a shop STATES about its own policies, each fact with the date it was last checked and where it was read: return window in days (returns_days), free return label, tracking offered, payment methods, buyer-protection seal, plus the shipping statement (destinations, stated delivery time, free-shipping threshold). Answers questions such as "how long can I return something at this shop?". These are shop-level statements, NOT offers and NOT quotes: no carrier, no shipping price. Every fact in `policies` is an object with `collected`: when true it carries value, checked_at and source (policy_page = read from the shop, llm_gap_resolution = model-derived, not read from the shop); when false it carries a reason and means OpenShopGraph holds no checked value, a gap in the data and NOT a statement that the shop has no such policy. A fact whose value and check date are stored but whose source is unknown is also reported as collected:false (reason no_source): a value without a source is not shown. The optional country (ISO 3166-1 alpha-2, e.g. "DE") adds a ships_to verdict derived from the stated destination list; "unknown" is a real answer there. `checked_at` is the date a figure was last checked and marks how current a stated claim is.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get shop policies
  • list_categoriesList the shop categories OpenShopGraph carries (for example fashion or electronics), to filter the shop search by category.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    List the shop categories OpenShopGraph carries (for example fashion or electronics), to filter the shop search by category. The taxonomy: every category slug currently carried by at least one public shop, together with how many public shops carry it. The taxonomy is flat (no parent/child hierarchy, e.g. "fashion" and "womens-clothing" are siblings, not nested) and its slugs come from observed data, not from a fixed enum, so the set of slugs is known only from this response. The `category` filter of the shop search accepts only slugs from this response. A shop can carry more than one category, so the counts can add up to more than the number of shops.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List categories
  • list_couponsList currently usable, source-dated discount codes for online shops, with verification status and what was withheld and why (an extra next to the shop facts).1 finding

    Why it is in this group

    • The name "list_coupons" says "list": a word for reading.

    Findings

    • Info

      The description is 2,951 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...(ISO timestamp of that reading); each is null when the record does not carry it."

      What this check looks for
    Description, as the server wrote it
    List currently usable, source-dated discount codes for online shops, with verification status and what was withheld and why (an extra next to the shop facts). Optionally filtered by shop_domain (e.g. "otto.de"). A code is withheld from `results` when it is EXPIRED (valid_until has passed), when a real checkout test PROVED it does not work (verification_status "verified_rejected"), or when a display policy suppresses it on this channel/country. Nothing is withheld silently: `total_count` is the REAL number of codes the query found before any of that (for the collection list the full count over everything, not just the window), `examined` is how many codes this request looked at, and `withheld` breaks the difference down by reason ({expired, verified_rejected, reserved_test_domain, policy}); examined minus results.length equals the sum of `withheld`, and `note` states the same balance in one sentence. WITHOUT shop_domain the answer is one window of at most `limit` codes (default 100, max 100) starting at `offset` (default 0), ordered by a stable id: `truncated` is true when more codes lie beyond it and `next_offset` is the offset of the next page (null on the last page), so `truncated: false` marks the last page. limit/offset are rejected together with shop_domain, which already returns every code of that shop. An empty `results` is explained by `total_count` and `note`, which tell "this shop has no codes at all" apart from "it has codes and every one of them is proven dead". An UNKNOWN or internal-review shop_domain is a different answer again: it is an error ("shop not found"), not an empty list; and a backend failure is reported as a failure, not as an empty list. Each result carries validUntil: an ISO timestamp when the code has a stated expiry, or null when it is open-ended; null means unlimited, NOT unknown-and-expired, and a stated expiry can pass after the response was produced. Each result ALSO carries verificationStatus, the verdict of a real checkout test against this exact code: "verified_applied" means the code worked in an actual checkout attempt (the response carries no stored proof artifact); "unverified" means no proof exists either way yet: it is unknown, not a negative signal, and does not mean the code was tested and failed. ("verified_rejected" is defined as before but no longer appears in `results`; it is counted in `withheld.verified_rejected` instead.) lastVerifiedAt is the ISO timestamp of that most recent test, or null if the code has not been tested. A non-null lastVerifiedAt on an "unverified" code means it WAS tested but the test was inconclusive, which is not the same as a code for which no test was attempted. Each result also states where the code came from: source (how it was obtained, e.g. "shop-owned-page" = read from the shop's own page), source_url (the page it was read on) and seen_at (ISO timestamp of that reading); each is null when the record does not carry it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List coupons

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 2 to 0

Findings

Matches of fixed checks, with the text they matched.

2 info
  • The description is 3,157 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...uery` (AND, not OR); `query: ""` browses a category without a name/domain filter."

    What this check looks for
  • The description is 2,951 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...(ISO timestamp of that reading); each is null when the record does not carry it."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 0.View diff
    • Tools that change things, listed without credentials: 2 to 0
  3. Tools3 removed, 6 changed.−3 removed~6 changedView diff
    • Removed:get_trust
    • Removed:report_code
    • Removed:report_issue
    • Changed:find_shopOnly readstitledescriptionannotations
    • Changed:get_shipping_policyOnly readstitledescriptionannotations
    • Changed:get_shopOnly readstitledescriptionannotations
    • Changed:get_shop_policiesOnly readstitledescriptionannotations
    • Changed:list_categoriesOnly readstitledescriptionannotations
    • Changed:list_couponsOnly readstitledescriptionannotations

Install

Pinned to version 0.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http openshopgraph https://api.openshopgraph.com/mcp
claude mcp add --transport http openshopgraph https://api.openshopgraph.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__openshopgraph__find_shop",
      "mcp__openshopgraph__list_categories",
      "mcp__openshopgraph__get_shop",
      "mcp__openshopgraph__list_coupons",
      "mcp__openshopgraph__get_shop_policies",
      "mcp__openshopgraph__get_shipping_policy"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as openshopgraph. Review it before you use it.

Capability tags behind 1 rule
  • mcp__openshopgraph__find_shop untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.openshopgraph/mcp/verify?hash=4854c25d40c9cd2a4d70ed71f425016e2c0c238fb04fba9dfba9c060edf6af31" | jq -e '.changed == false'

Pinned hash 4854c25d40c9, from Nov 10, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.openshopgraph/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.openshopgraph/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.openshopgraph/mcp.svg)](https://radar.anlyon.com/servers/com.openshopgraph/mcp)

Source: MCP Registry. Synced Oct 28, 2026, 23:17 UTC.

OpenShopGraph MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OpenShopGraph MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the OpenShopGraph MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the OpenShopGraph MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the OpenShopGraph MCP server have?

6 tools: 6 read. find_shop, list_categories, get_shop, list_coupons, get_shop_policies and get_shipping_policy.

Does the OpenShopGraph MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the OpenShopGraph MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the OpenShopGraph MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.