mcpbeat

Shopgraph MCP Server

io.github.laundromatic/shopgraph
not responding

Shopgraph is listed as active in the registry but did not answer our last check. 26 installs a week from npm. It exposes 4 tools.

Clean product data from any URL. Schema.org + AI extraction. 200 free calls/month.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 23 · avg 6 · -21% w/w
a month agotoday
Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
4
Tools
read from the server
180 ms
Response time
average over 24h
26
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add shopgraph --transport http https://shopgraph.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "shopgraph": {
      "url": "https://shopgraph.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.shopgraph]
url = "https://shopgraph.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "shopgraph": {
      "url": "https://shopgraph.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "shopgraph": {
      "url": "https://shopgraph.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

enrich
enrich_basic
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.
enrich_html
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.
enrich_product
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.
score
score_product
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.

Endpoints

URLTransportStateLatencyChecked
https://shopgraph.dev/mcp streamable-http answering 180 ms 14 min ago

Shopgraph — questions

Answers built from our own checks of this server.

What can Shopgraph do?
It exposes 4 tools, read directly from the server on our last check. Among them: enrich_basic, enrich_html, enrich_product, score_product. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Shopgraph working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 180 ms. The bar chart above shows every period we have measured.
Is Shopgraph still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Shopgraph as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Shopgraph?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Shopgraph need an API key?
No. Shopgraph completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How many people use Shopgraph?
The npm package shopgraph was installed 26 times in the last week. Week over week that is -21%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.