Shopgraph MCP server

• enrich_basicFree

  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_htmlFree

  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_productFree

  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_productFree

  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.

• Code scan5 source files scanned25/25
• Live reliabilityremote reachable in 798ms20/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

75/100

higher than 50% of 2,174 E-commerce servers

Tools

4

the typical E-commerce server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote E-commerce server answers 100%

Response time

347 ms

faster than 45% of 1,527 E-commerce servers

Downloads a week

31

more than 23% of 411 E-commerce servers with a package

Shopgraph: common questions

Is Shopgraph MCP server safe?

Mostly: it is graded B (75/100). Read the Shopgraph safety report

How do I install Shopgraph?

It runs remotely at shopgraph.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Shopgraph need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Shopgraph maintained?

The latest release is v1.0.1.

Is Shopgraph up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Shopgraph?

Servers from other publishers that do the same job: COTAL actions (cotal.ai) MCP server, PostHog MCP Server and Loki Mode MCP server.

How does Shopgraph compare with other E-commerce MCP servers?

safety score 75/100 (higher than 50% of 2,174 E-commerce servers); tools 4 (the typical E-commerce server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.