io.github.laundromatic/shopgraph
REMOTE · SHOPGRAPH.DEV · 2 COMPONENTS
Clean product data from any URL. Schema.org + AI extraction. 200 free calls/month.
Available components
Last scanned (39 minutes ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1058 tokens (~211/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://shopgraph.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.shopgraph.dev | CN=YR1,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 5947e109cb0934b0b9966b224c0037c1567 |
| SANs: *.shopgraph.dev, shopgraph.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of shopgraph.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| shopgraph.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shopgraph.dev/mcp | Verified | 200 | |
| http (plaintext) | http://shopgraph.dev/mcp | HTTPS enforced | 308 | https://shopgraph.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
enrich_basic ~301
Extract basic product attributes from a URL (name, price, brand, availability). Faster and cheaper than enrich_product. 50 free calls/month — no payment needed. Paid: $0.01 per call after free tier. Each field carries verification metadata in _shopgraph: provenance (field_method — which source/tier produced it: schema_org, llm, or hybrid), freshness (field_freshness — recency + volatility_class, for volatile fields like price & availability), and abstain (a field is null when ShopGraph cannot verify it on the page). Rely on provenance, freshness, and the abstain signal to decide what to trust.
| Name | Type | Req | Description |
|---|---|---|---|
| force_refresh | boolean | – | Bypass cache entirely. Always triggers live extraction. Costs 3x credits. |
| format | string | – | Output format. "ucp" returns UCP line_item format. Default: "default". |
| include_score | boolean | – | Include agent-readiness score in response. |
| minimum_confidence | number | – | Auto-refresh if any cached field's DECAYED confidence falls below this threshold. Costs 2x credits when refresh triggers, 0.25x on cache hit. |
| payment_method_id | string | – | Stripe payment method ID for MPP payment |
| strict_confidence_threshold | number | – | Fields below this confidence will be nulled with explanation. Default: off. |
| url | string | yes | Product page URL to extract data from |
No output schema declared.
No examples provided.
enrich_html ~317
Extract product data from raw HTML you already have (no HTTP fetch needed). Ideal when using Bright Data, Firecrawl, or any scraping API — pipe the HTML through ShopGraph for structured product data. Uses schema.org + LLM fallback. Costs $0.02 per call (cached results are free). Each field carries verification metadata in _shopgraph: provenance (field_method — which source/tier produced it: schema_org, llm, or hybrid), freshness (field_freshness — recency + volatility_class, for volatile fields like price & availability), and abstain (a field is null when ShopGraph cannot verify it on the page). Rely on provenance, freshness, and the abstain signal to decide what to trust.
| Name | Type | Req | Description |
|---|---|---|---|
| force_refresh | boolean | – | Bypass cache entirely. Always triggers live extraction. Costs 3x credits. |
| format | string | – | Output format. "ucp" returns UCP line_item format. Default: "default". |
| html | string | yes | Raw HTML content of the product page |
| include_score | boolean | – | Include agent-readiness score in response. |
| minimum_confidence | number | – | Auto-refresh if any cached field's DECAYED confidence falls below this threshold. |
| payment_method_id | string | – | Stripe payment method ID for MPP payment |
| strict_confidence_threshold | number | – | Fields below this confidence will be nulled with explanation. Default: off. |
| url | string | yes | Original URL of the page (used for context and caching) |
No output schema declared.
No examples provided.
enrich_product ~303
Extract comprehensive product data from a URL including name, price, brand, images, availability, and more. Uses schema.org structured data when available, with LLM fallback. Costs $0.02 per call (cached results are free). Each field carries verification metadata in _shopgraph: provenance (field_method — which source/tier produced it: schema_org, llm, or hybrid), freshness (field_freshness — recency + volatility_class, for volatile fields like price & availability), and abstain (a field is null when ShopGraph cannot verify it on the page). Rely on provenance, freshness, and the abstain signal to decide what to trust.
| Name | Type | Req | Description |
|---|---|---|---|
| force_refresh | boolean | – | Bypass cache entirely. Always triggers live extraction. Costs 3x credits. |
| format | string | – | Output format. "ucp" returns UCP line_item format. Default: "default". |
| include_score | boolean | – | Include agent-readiness score in response. |
| minimum_confidence | number | – | Auto-refresh if any cached field's DECAYED confidence falls below this threshold. Costs 2x credits when refresh triggers, 0.25x on cache hit. |
| payment_method_id | string | – | Stripe payment method ID for MPP payment |
| strict_confidence_threshold | number | – | Fields below this confidence will be nulled with explanation. Default: off. |
| url | string | yes | Product page URL to extract data from |
No output schema declared.
No examples provided.
score_product ~126
Extract product data and return agent-readiness score (0-100). Scores structured data completeness, semantic richness, UCP compatibility, pricing clarity, and inventory signals. Full scoring breakdown included.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format. "ucp" returns UCP line_item format. Default: "default". |
| payment_method_id | string | – | Stripe payment method ID for MPP payment |
| strict_confidence_threshold | number | – | Fields below this confidence will be nulled with explanation. Default: off. |
| url | string | yes | Product page URL to extract and score |
No output schema declared.
No examples provided.
How do I install the io.github.laundromatic/shopgraph MCP server?
io.github.laundromatic/shopgraph is a hosted endpoint at https://shopgraph.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · shopgraph.dev
claude mcp add --transport http laundromatic-shopgraph 'https://shopgraph.dev/mcp'
What is the io.github.laundromatic/shopgraph MCP server?
io.github.laundromatic/shopgraph is an MCP server listed in the public MCP registry as io.github.laundromatic/shopgraph. Clean product data from any URL. Schema.org + AI extraction. 200 free calls/month. This page covers its hosted endpoint (https://shopgraph.dev/mcp).
Is the io.github.laundromatic/shopgraph MCP server safe to use?
io.github.laundromatic/shopgraph scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.laundromatic/shopgraph MCP server expose?
io.github.laundromatic/shopgraph exposes 4 tools: enrich_product, enrich_basic, enrich_html, score_product. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.
Does the io.github.laundromatic/shopgraph MCP server require authentication?
No. We connected to io.github.laundromatic/shopgraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.laundromatic/shopgraph MCP server still maintained?
io.github.laundromatic/shopgraph is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.