# OpenShopGraph (remote · api.openshopgraph.com)

Open, verified shop database for AI agents: products, offers, price comparison, trust and coupons.

- Trust score: 67/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `api.openshopgraph.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-openshopgraph-mcp/api.md), [page](https://verifymcp.io/servers/com-openshopgraph-mcp/api)

## Channel facts

- Endpoint: `https://api.openshopgraph.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1221 tokens (~203/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 6/100
  - Stability check failed: schema churn in the 10 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

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

### Codex

```toml
[mcp_servers.com-openshopgraph-mcp]
url = "https://api.openshopgraph.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-openshopgraph-mcp": {
      "type": "remote",
      "url": "https://api.openshopgraph.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-openshopgraph-mcp --url https://api.openshopgraph.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-openshopgraph-mcp:
    url: "https://api.openshopgraph.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-openshopgraph-mcp": {
      "type": "http",
      "url": "https://api.openshopgraph.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 6.

### 2026-08-14 (score 66, +1)

- [security] Tool “find_shop” rewrote its description, which is the text the model reads
- [security] Tool “list_coupons” rewrote its description, which is the text the model reads
- [cosmetic] “get_shipping_policy” reworded the description of “shop_domain”
- [cosmetic] “get_shop” reworded the description of “shop_domain”
- [cosmetic] “get_trust” reworded the description of “shop_domain”

### 2026-08-13 (score 65, −1)

- [security] Tool “find_shop” rewrote its description, which is the text the model reads
- [cosmetic] “find_shop” added an optional parameter “limit”
- [cosmetic] “find_shop” added an optional parameter “offset”

### 2026-08-11 (score 66, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 67)

First indexed and scored.

## MCP tools (6)

### `find_shop` (~264 tokens)

Search merchants/shops by free-text query (name or domain fragment), optionally filtered by country (ISO 3166-1 alpha-2, e.g. "DE"). Returns the public shop view only — shops still under internal review are never 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 this page — raise `offset` (default 0) to page through them. 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 you asked, so do not present them as satisfying those words. `category_truncated` is true when category resolution hit its internal cap and the match set is a subset. If many shops match, grouping by country or category keeps the list scannable.

Input parameters:

- `country` (string)
- `limit` (number)
- `offset` (number)
- `query` (string, required)

### `get_shop` (~131 tokens)

Fetch a single merchant/shop by id or domain (public view). Returns "shop not found" for shops still under internal review, identical to a genuinely unknown domain — reviewers cannot be distinguished from typos. The offers array is present for schema stability but empty until merchant offers are ingested (Offer table measured empty on 2026-07-30).

Input parameters:

- `shop_domain` (string, required): Shop domain, e.g. "otto.de". An internal OpenShopGraph shop id is accepted here as well. The older field name `shop_id_or_domain` still works on every tool and means exactly the same thing.

### `list_coupons` (~147 tokens)

List currently visible discount codes/coupons, optionally filtered by shop_domain (e.g. "otto.de"). Only publicly displayable coupons are returned — internal/candidate-shop or policy-suppressed codes are excluded, and EXPIRED codes are never returned (a code whose valid_until has passed is withheld). 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. Re-check validUntil against the current time before relaying a code; including the shop domain and the expiry avoids sending users to codes that will not apply for them.

Input parameters:

- `shop_domain` (string)

### `get_shipping_policy` (~257 tokens)

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. Pass country (ISO 3166-1 alpha-2, e.g. "DE") to get 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): that is a gap in the data, not a statement that the shop does not ship. Relaying the checked-at date alongside any figure keeps a stale merchant claim from being read as a current fact.

Input parameters:

- `country` (string)
- `shop_domain` (string, required): Shop domain, e.g. "otto.de". An internal OpenShopGraph shop id is accepted here as well. The older field name `shop_id_or_domain` still works on every tool and means exactly the same thing.

### `get_trust` (~250 tokens)

Trust-relevant facts OpenShopGraph itself measured about one merchant/shop (by id or domain): TLS certificate issuer and grade, hosting ISP and country, domain registration date, registrar, and accepted payment methods. Returns INDIVIDUAL signals, never an aggregate: every entry carries its own value, `source` (where OpenShopGraph observed it) and `checked_at` (when). There is deliberately no score, rating, percentage or star value — not even an internally computed one; you are given the raw evidence and judge for yourself. A field with no source or no check timestamp is omitted entirely rather than shipped with a null placeholder. If nothing was measured, the answer is status "no_signals_collected" with an empty list — that means NOTHING IS KNOWN, it is not a score of zero and not a negative verdict. Unknown domains, shops under internal review and measured-but-empty shops are intentionally indistinguishable here.

Input parameters:

- `shop_domain` (string, required): Shop domain, e.g. "otto.de". An internal OpenShopGraph shop id is accepted here as well. The older field name `shop_id_or_domain` still works on every tool and means exactly the same thing.

### `report_code` (~118 tokens)

Record that a specific shop_domain + code (coupon) pair was tried and the outcome (invalid, expired, store_specific, or worked). This is a write: it appends one new report row and never deletes or overwrites existing data — it does not change what list_coupons returns immediately, since reports feed aggregate signals over time. No PII is accepted or stored (note text is scrubbed).

Input parameters:

- `code` (string, required)
- `note` (string)
- `reason` (required)
- `shop_domain` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-openshopgraph-mcp/api#diagnostics

## Score history

- 2026-08-20: 67
- 2026-08-19: 66
- 2026-08-18: 66
- 2026-08-17: 66
- 2026-08-16: 66
- 2026-08-15: 66
- 2026-08-14: 66
- 2026-08-13: 65
- 2026-08-12: 66
- 2026-08-11: 66
- 2026-08-10: 67

## Links

- Remote endpoint: https://api.openshopgraph.com/mcp
- Website: https://openshopgraph.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-openshopgraph-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-openshopgraph-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-openshopgraph-mcp/api