Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Full product feed hygiene scan of a product feed URL (Google Shopping-style XML, CSV, or JSON — format auto-detected). Fetches the feed server-side and runs 20 weighted checks: parse validity and encoding, required attributes (id, title, link, price, availability values, image_link), GTIN/MPN and brand coverage, identifier_exists misuse, title/description quality, image-link spot-checks, price format and sale_price logic, taxonomy and shipping/tax presence, duplicate ids and variant grouping. These are the errors behind Google Merchant Center disapprovals — a disapproved feed means the products do not serve on Google Shopping at all, and agent-commerce surfaces referencing Merchant Center IDs inherit the same dirt. Returns machine-readable JSON: 0-100 score, A-F grade, a disapproval-risk level (Low/Moderate/Elevated/High) with the failing disapproval-class checks named, per-check pass/partial/fail/unknown with evidence, the worst-offending items sampled with concrete fixes, and the top 3 prioritized fixes. HONEST LIMITS: the scan validates the feed document (capped at 8 MB, first 20,000 items, 8 image spot-checks); it does not crawl landing pages, so feed-vs-page price/availability mismatches are out of scope. Cost: $1.00 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this after every catalog change, before a Shopping campaign launch, or to triage a disapproval wave.
Product feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http feed-audit https://feed-al6bxcngia-ue.a.run.app/mcp
Full product feed hygiene scan of a product feed URL (Google Shopping-style XML, CSV, or JSON — format auto-detected). Fetches the feed server-side and runs 20 weighted checks: parse validity and encoding, required attributes (id, title, link, price, availability values, image_link), GTIN/MPN and brand coverage, identifier_exists misuse, title/description quality, image-link spot-checks, price format and sale_price logic, taxonomy and shipping/tax presence, duplicate ids and variant grouping. These are the errors behind Google Merchant Center disapprovals — a disapproved feed means the products do not serve on Google Shopping at all, and agent-commerce surfaces referencing Merchant Center IDs inherit the same dirt. Returns machine-readable JSON: 0-100 score, A-F grade, a disapproval-risk level (Low/Moderate/Elevated/High) with the failing disapproval-class checks named, per-check pass/partial/fail/unknown with evidence, the worst-offending items sampled with concrete fixes, and the top 3 prioritized fixes. HONEST LIMITS: the scan validates the feed document (capped at 8 MB, first 20,000 items, 8 image spot-checks); it does not crawl landing pages, so feed-vs-page price/availability mismatches are out of scope. Cost: $1.00 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this after every catalog change, before a Shopping campaign launch, or to triage a disapproval wave.
| Argument | Type | Description |
|---|---|---|
| url* | string | Product feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml |
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Product feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml"
}
}
}FREE lite product feed hygiene scan of a product feed URL (XML, CSV, or JSON — auto-detected). Runs the same 20 checks as audit_feed but returns top-line results only: 0-100 score, A-F grade, disapproval-risk level, detected format, item count, check counts, and the titles of the top gaps — item-level detail is capped (no per-check evidence, no offending items, no detailed fixes). Use this to triage whether a feed needs the full audit_feed report, or call audit_feed directly for the complete evidence-backed scan.
| Argument | Type | Description |
|---|---|---|
| url* | string | Product feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml |
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Product feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 13, 2026.