Bring Your AI
REMOTE · BRINGYOUR.AI
No-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime.
Available components
Last scanned (4 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Security63
- 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 7 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 600 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 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
- 27 Aug 26 0
- Tool “quote_lifetime_license” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass 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
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 5 Nov 2026 · Probed https://bringyour.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bringyour.ai | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6ac0e5989c776e48e6a1d704a44144aebb0 |
| SANs: bringyour.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bringyour.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| bringyour.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bringyour.ai/mcp | Verified | 200 | |
| http (plaintext) | http://bringyour.ai/mcp | HTTPS enforced | 301 | https://bringyour.ai/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 →
install_local_cli ~49
Return no-data local install and MCP wiring commands. The remote server does not install anything and does not receive harness data.
| Name | Type | Req | Description |
|---|---|---|---|
| target_agent | string | – | Optional: claude-code or codex. |
No output schema declared.
No examples provided.
list_products ~26
List agent-readable Bring Your AI products and supported payment modes. No harness data is accepted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_targets ~23
List Bring Your AI target tools. No harness data is accepted or returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_build_setup ~74
Free no-data preview for building a user's first setup in any of the 13 supported tools. Does not accept GitHub handles, generated memories, mappings, or file content.
| Name | Type | Req | Description |
|---|---|---|---|
| to | string | yes | Target tool id, e.g. claude-code, codex, cursor. Use list_targets for the full matrix. |
No output schema declared.
No examples provided.
preview_move ~174
Free no-data preview for moving a harness between any two of the 13 supported tools (Claude Code, Cursor, Codex, OpenClaw, Aider, Continue, Cline, Goose, Zed, Roo Code, ChatGPT, Claude.ai, Copilot). Returns feasibility copy only. Does not accept or return mappings, file paths, generated content, or validation notes.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Source tool id, e.g. claude-code, cursor, codex, openclaw, aider, continue, cline, goose, zed, roo, chatgpt, claude-ai. Use list_targets for the full matrix. |
| to | string | yes | Target tool id, e.g. codex, cursor, claude-code, copilot. Use list_targets for the full matrix. |
No output schema declared.
No examples provided.
quote_lifetime_license ~104
Quote a Bring Your AI lifetime license or Team Migration Pack in USD. The team pack includes one guided migration and onboarding for up to 10 people plus lifetime licenses.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_country | string | – | Optional ISO country code. |
| currency | string | – | Optional requested currency. Only USD is currently supported. |
| locale | string | – | Optional BCP 47 locale. |
| product_id | string | – | Optional product id. Defaults to bringyour_founder_lifetime. |
No output schema declared.
No examples provided.
start_checkout ~150
Start checkout. With payment_mode=stripe_spt plus shared_payment_granted_token and buyer_email, settles a Stripe PaymentIntent and returns the signed license without opening a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_email | string | – | Email bound to the issued license. Required for stripe_spt settlement. |
| string | – | Alias for buyer_email. | |
| payment_mode | string | – | stripe_payment_link, stripe_link, link, stripe_checkout, stripe_acp, stripe_spt, or x402. |
| product_id | string | – | Optional product id. Defaults to bringyour_founder_lifetime. |
| shared_payment_granted_token | string | – | Link-issued Stripe shared payment token. Required for stripe_spt settlement. |
No output schema declared.
No examples provided.
How do I install the Bring Your AI MCP server?
Bring Your AI is a hosted endpoint at https://bringyour.ai/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 · bringyour.ai
claude mcp add --transport http ai-bringyour-bringyour 'https://bringyour.ai/mcp'
What is the Bring Your AI MCP server?
Bring Your AI is an MCP server listed in the public MCP registry as ai.bringyour/bringyour. No-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime. This page covers its hosted endpoint (https://bringyour.ai/mcp).
Is the Bring Your AI MCP server safe to use?
Bring Your AI scores 79 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 Bring Your AI MCP server expose?
Bring Your AI exposes 7 tools: preview_move, preview_build_setup, list_targets, install_local_cli, list_products, and 2 more. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Does the Bring Your AI MCP server require authentication?
No. We connected to Bring Your AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bring Your AI MCP server still maintained?
Bring Your AI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.