productschema

Audit a store's product page and get the JSON-LD Product markup it is missing. No account.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~200Tokens (tool definitions)
~639 BTypical response size
Minimal attention impact (0.16% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "productschema": {
      "url": "https://productschema.pages.dev/mcp"
    }
  }
}

Remote endpoints

https://productschema.pages.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢audit_product_page(url)

Checks whether an online store can be read and cited by AI shopping assistants, and returns a ready-to-paste JSON-LD Product snippet built from what is actually on the page. Measures: which AI crawlers robots.txt lets in, whether the page renders without JavaScript, which Product fields (price, availability, GTIN, rating, returns, shipping) are present in structured data, title/meta, and sitemap reachability. Everything reported is derived from bytes fetched live — no estimates. Give it a storefront domain or a direct product URL; a product page gives the most useful result.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Store domain or product URL, e.g. \"example.com\" or \"https://example.com/products/thing\"."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools
verifiedversion not recorded1 tools