Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BridgeToAgent — AI Readiness

REMOTE · WWW.BRIDGETOAGENT.COM · SCANNED SEP 21

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

0 this week 26 Trust /100
Trust breakdown (7 categories)

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 Security66
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.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.

Install

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

# add to Claude Code
claude mcp add --transport http com-bridgetoagent-ai-readiness 'https://www.bridgetoagent.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-bridgetoagent-ai-readiness": {
      "url": "https://www.bridgetoagent.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-bridgetoagent-ai-readiness": {
      "type": "http",
      "url": "https://www.bridgetoagent.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-bridgetoagent-ai-readiness]
url = "https://www.bridgetoagent.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bridgetoagent-ai-readiness": {
      "type": "remote",
      "url": "https://www.bridgetoagent.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-bridgetoagent-ai-readiness --url 'https://www.bridgetoagent.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-bridgetoagent-ai-readiness:
    url: "https://www.bridgetoagent.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-bridgetoagent-ai-readiness": {
      "Transport": "http",
      "Url": "https://www.bridgetoagent.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-bridgetoagent-ai-readiness -t streamable-http -u 'https://www.bridgetoagent.com/api/mcp'
// mcp.json
{
  "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.

Changelog

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.

  • 26 Aug 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
  • 12 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP security
  • 11 Aug 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
  • 31 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
  • 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 0

    First indexed and scored.

Diagnostics

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 21 Sept 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

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 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 404
Header Value
strict-transport-security max-age=63072000

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 HTTP error 404
http (plaintext) http://www.bridgetoagent.com/api/mcp HTTPS enforced 308 https://www.bridgetoagent.com/api/mcp
MCP tools · 2 exposed · ~259 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
urlstringyesThe store's URL or domain, e.g. 'example.com' or 'https://example.com'.

No output schema declared.

No examples provided.

simulate_agent_shopping ~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.

NameTypeReqDescription
urlstringyesThe store's URL or domain, e.g. 'example.com' or 'https://example.com'.

No output schema declared.

No examples provided.

Common questions

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).

Is the BridgeToAgent — AI Readiness MCP server safe to use?

BridgeToAgent — AI Readiness scores 26 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

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?

No. We connected to BridgeToAgent — AI Readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BridgeToAgent — AI Readiness MCP server still maintained?

BridgeToAgent — AI Readiness is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.