mcp server
BridgeToAgent — AI Readiness
Is a website ready for AI shopping agents? Readiness score (0-100) + agent shopping simulation.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-06-02.
What this server can do
The endpoint published in the registry did not answer (HTTP 404). The listing points at a server that is not running. The functions below are the last successful declaration, not a fresh answer.
Endpoint status observed on . Source: https://www.bridgetoagent.com/api/mcp.
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_ai_readiness(url)- Check whether a website or online store is ready for AI agents — whether assistants like ChatGPT, Claude, and Perplexity can read it, recommend it, and act on it. Returns an AI-readiness score (0–100) and which agent-readiness files the site exposes (agents.json, llms.txt, agent-instructions.md, structured data). Use this when a user asks if their store/site is AI-ready, visible to AI, or ready for AI shopping. Required: url.
simulate_agent_shopping(url)- Send an AI shopping agent at a store and report, task by task, what it can and can't do autonomously — understand the catalog, find a product, add to cart, find the return policy, complete checkout — grounded in the real signals the site exposes. Returns the agent's first-person verdict and where it gets stuck. Use this when a user wants to SEE how an AI agent would experience shopping their (or any) store. Required: url.
Last successful function declaration observed on . Source: https://www.bridgetoagent.com/api/mcp. We list what the server declared; we do not call any of these functions.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.bridgetoagent.com | |
| mcp endpoint status | unreachable | The endpoint published in the registry did not answer (HTTP 404). The listing points at a server that is not running. | as of probe | www.bridgetoagent.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json