BridgeToAgent — AI Readiness
REMOTE · WWW.BRIDGETOAGENT.COM · SCANNED AUG 3
Is a website ready for AI shopping agents? Readiness score (0-100) + agent shopping simulation.
Available components
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 →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 259 tokens (~129/item across 2 items; 2 tools + 0 resources), lean.Pass
- 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.bridgetoagent.com
claude mcp add --transport http com-bridgetoagent-ai-readiness https://www.bridgetoagent.com/api/mcp
[mcp_servers.com-bridgetoagent-ai-readiness] url = "https://www.bridgetoagent.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bridgetoagent-ai-readiness": {
"type": "remote",
"url": "https://www.bridgetoagent.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-bridgetoagent-ai-readiness --url https://www.bridgetoagent.com/api/mcp --transport streamable-http
mcp_servers:
com-bridgetoagent-ai-readiness:
url: "https://www.bridgetoagent.com/api/mcp" {
"mcpServers": {
"com-bridgetoagent-ai-readiness": {
"type": "http",
"url": "https://www.bridgetoagent.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 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
- 26 Jul 26 66
First indexed and scored.
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 3 Aug 2026 · Probed https://www.bridgetoagent.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| 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 |
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 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.bridgetoagent.com/api/mcp | Verified | 200 | |
| 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.
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.