mcpbeat

BridgeToAgent — AI Readiness MCP Server

com.bridgetoagent/ai-readiness
not responding

BridgeToAgent — AI Readiness is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Is a website ready for AI shopping agents? Readiness score (0-100) + agent shopping simulation.

Uptime history 43 hours of history · worst hour 0%
43 hours agonow
49.5%
Uptime 24h
45 of 91 checks
2
Tools
read from the server
379 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add ai-readiness --transport http https://www.bridgetoagent.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-readiness": {
      "url": "https://www.bridgetoagent.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai-readiness]
url = "https://www.bridgetoagent.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-readiness": {
      "url": "https://www.bridgetoagent.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai-readiness": {
      "url": "https://www.bridgetoagent.com/api/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

readiness
check_ai_readiness
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.
simulate
simulate_agent_shopping
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.

Endpoints

URLTransportStateLatencyChecked
https://www.bridgetoagent.com/api/mcp streamable-http answering 51 ms 10 min ago

BridgeToAgent — AI Readiness — questions

Answers built from our own checks of this server.

What can BridgeToAgent — AI Readiness do?
It exposes 2 tools, read directly from the server on our last check. Among them: check_ai_readiness, simulate_agent_shopping. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is BridgeToAgent — AI Readiness working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 45 of 91 checks got a reply (49.5%), average response time 379 ms. The bar chart above shows every period we have measured.
The registry lists BridgeToAgent — AI Readiness as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect BridgeToAgent — AI Readiness?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does BridgeToAgent — AI Readiness need an API key?
No. BridgeToAgent — AI Readiness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is BridgeToAgent — AI Readiness?
It answers our handshake in 379 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.