Find AI-ready merchant feeds: resolve a store domain to its ID and fetch full product detail.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-bluestratus-agenticfeed": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An open specification for making ecommerce product catalogues readable by AI shopping agents.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ecommerce
Argentine business automation: Mercado Pago, AFIP/ARCA, WhatsApp, banking, shipping (7 packages).
A command line tool for setting up commercetools MCP server
Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.
35+ AI tools for TCG card grading, Monte Carlo pricing, 370K+ product search. BYOK.
MCP Security Weekly
Get CVE alerts and security updates for io.github.bluestratus/agenticfeed and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An open specification for making ecommerce product catalogues readable by AI shopping agents.
AI assistants like ChatGPT, Claude, Perplexity, and Gemini are already recommending products to millions of shoppers. They do not browse category pages or read banner ads. They consume structured data and reason about which products best match the buyer's intent. Most merchant websites are invisible to them.
This standard defines a lightweight, discoverable format that gives AI agents exactly what they need.
Add one line to the <head> of every page on your website:
<link rel="agenticfeed" type="application/json" href="https://yourdomain.com/feed.json">
That tag tells any AI agent or crawler where your structured product feed lives. The rest of this document describes what that feed should contain.
An agentic feed is a structured product data feed built for AI agents rather than search engine crawlers or human browsers.
A traditional product page is designed to be rendered and read by a person. A Google Merchant Center feed is designed to be parsed by a price comparison engine. An agentic feed is designed to be reasoned about by an AI.
The key difference is intent data. Where a merchant feed tells an agent "here is a cordless drill, it costs £29.99 and it is in stock," an agentic feed tells it "here is a cordless drill that answers the question what drill do I need for assembling flat-pack furniture, solves the problem I keep stripping screws with my old drill, and fits the use case home DIY for a first-time homeowner."
That is the layer of context an AI agent needs to make a confident recommendation to a specific buyer.
AI shopping is already happening. The tooling to serve it well does not yet exist as an open, portable standard.
Search engines standardised web content discovery through sitemaps, robots.txt, and canonical tags. RSS standardised content syndication through a single autodiscovery tag. Neither was designed for the kind of structured reasoning that AI agents perform when they decide what to recommend.
This specification fills that gap. It defines:
The format is intentionally minimal. It builds on schema.org types that crawlers already understand. It adds the intent layer that makes AI recommendation possible