BridgeToAgent — AI Readiness
REMOTE · WWW.BRIDGETOAGENT.COM
Is a website ready for AI shopping agents? Readiness score (0-100) + agent shopping simulation.
Available components
Last scanned (21 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 4 Oct 2026.
Category E-commerce
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
Recent critical change
TLS certificate (7 Oct 2026). See the changelog before you install this server.
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 Security14
- TLS check failed: the certificate is expired or not yet valid (as of 2026-10-04). See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 15 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Oct 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Oct 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 15 Oct 2026 · Probed https://www.bridgetoagent.com/api/mcp
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: expired
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.bridgetoagent.com | CN=YR1,O=Let's Encrypt,C=US | 6 Jul 2026 | 4 Oct 2026 | RSA 2048 | SHA256-RSA | 57337f4d0fae05b6e085cd64247b07475af |
| SANs: www.bridgetoagent.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.bridgetoagent.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bridgetoagent.com. | present | 42829 | 13 | Verified |
| www.bridgetoagent.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.bridgetoagent.com/api/mcp | TLS failed | ||
| http (plaintext) | http://www.bridgetoagent.com/api/mcp | HTTPS enforced | 308 | https://www.bridgetoagent.com/api/mcp |
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 →
check_ai_readiness Check AI readiness ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's URL or domain, e.g. 'example.com' or 'https://example.com'. |
No output schema declared.
No examples provided.
simulate_agent_shopping Simulate an AI agent shopping the store ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The store's URL or domain, e.g. 'example.com' or 'https://example.com'. |
No output schema declared.
No examples provided.
How do I install the BridgeToAgent — AI Readiness MCP server?
BridgeToAgent — AI Readiness is a hosted endpoint at https://www.bridgetoagent.com/api/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 · www.bridgetoagent.com
claude mcp add --transport http com-bridgetoagent-ai-readiness 'https://www.bridgetoagent.com/api/mcp'
What is the BridgeToAgent — AI Readiness MCP server?
BridgeToAgent — AI Readiness is an MCP server listed in the public MCP registry as com.bridgetoagent/ai-readiness. Is a website ready for AI shopping agents? Readiness score (0-100) + agent shopping simulation. This page covers its hosted endpoint (https://www.bridgetoagent.com/api/mcp).
What tools does the BridgeToAgent — AI Readiness MCP server expose?
BridgeToAgent — AI Readiness exposes 2 tools: check_ai_readiness, simulate_agent_shopping. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.
Does the BridgeToAgent — AI Readiness MCP server require authentication?
Its publisher declares no required credentials for BridgeToAgent — AI Readiness. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BridgeToAgent — AI Readiness MCP server still maintained?
BridgeToAgent — AI Readiness has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.