Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Feed Audit (Product Feed Hygiene)

REMOTE · FEED-AL6BXCNGIA-UE.A.RUN.APP

Audits a product feed (XML/CSV/JSON) for Google Shopping disapproval errors. $1.00/call via x402.

+4 this week 75 Trust /100

Last scanned (12 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 522 tokens (~261/item across 2 items; 2 tools + 0 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 71

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://feed-al6bxcngia-ue.a.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 f668c9036838957b095b05d18ab2228d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff32d6b409d15d5965b05873a7c72e0
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of feed-al6bxcngia-ue.a.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
run.app. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://feed-al6bxcngia-ue.a.run.app/mcp Verified 200
http (plaintext) http://feed-al6bxcngia-ue.a.run.app/mcp HTTPS enforced 302 https://feed-al6bxcngia-ue.a.run.app/mcp
MCP tools · 2 exposed · ~522 tokens

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 →

Tool Tokens
audit_feed ~365

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.

NameTypeReqDescription
urlstringyesProduct feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml

No output schema declared.

No examples provided.

audit_feed_lite ~157

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.

NameTypeReqDescription
urlstringyesProduct feed URL to scan (XML, CSV, or JSON), e.g. https://example-store.com/feed.xml

No output schema declared.

No examples provided.

Install

How do I install the Feed Audit (Product Feed Hygiene) MCP server?

Feed Audit (Product Feed Hygiene) is a hosted endpoint at https://feed-al6bxcngia-ue.a.run.app/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 · feed-al6bxcngia-ue.a.run.app

# add to Claude Code
claude mcp add --transport http theharrisontruong-web-feed-audit 'https://feed-al6bxcngia-ue.a.run.app/mcp'
Common questions

What is the Feed Audit (Product Feed Hygiene) MCP server?

Feed Audit (Product Feed Hygiene) is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/feed-audit. Audits a product feed (XML/CSV/JSON) for Google Shopping disapproval errors. $1.00/call via x402. This page covers its hosted endpoint (https://feed-al6bxcngia-ue.a.run.app/mcp).

Is the Feed Audit (Product Feed Hygiene) MCP server safe to use?

Feed Audit (Product Feed Hygiene) scores 75 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 Feed Audit (Product Feed Hygiene) MCP server expose?

Feed Audit (Product Feed Hygiene) exposes 2 tools: audit_feed, audit_feed_lite. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.

Does the Feed Audit (Product Feed Hygiene) MCP server require authentication?

No. We connected to Feed Audit (Product Feed Hygiene) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Feed Audit (Product Feed Hygiene) MCP server still maintained?

Feed Audit (Product Feed Hygiene) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Feed Audit (Product Feed Hygiene) MCP server?

VerifyMCP ran 13 checks on Feed Audit (Product Feed Hygiene), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.