mcp-registry/ai.bringyour/bringyour · v1.0.0
As of 2026-10-22 21:37 UTC, the Bringyour MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 2 minutes.
No-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime.
Claude Code
claude mcp add --transport http bringyour-mcp-server https://bringyour.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bringyour-mcp-server": {
"type": "http",
"url": "https://bringyour.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.bringyour%2Fbringyour/fixes
{
"name": "list_products",
"description": "List agent-readable Bring Your AI products and supported payment modes. No harness data is accepted.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_targets",
"description": "List Bring Your AI target tools. No harness data is accepted or returned.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "preview_build_setup",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Target tool id, e.g. claude-code, codex, cursor. Use list_targets for the full matrix."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.bringyour/bringyour"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.bringyour/bringyour"}) over MCP.
start_checkout ~244 tokenspreview_move ~220 tokensquote_lifetime_license ~183 tokenspreview_build_setup ~121 tokensinstall_local_cli ~93 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.bringyour%2Fbringyour?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.bringyour%2Fbringyour?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.bringyour%2Fbringyour.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.bringyour%2Fbringyour.svg :target: https://glimind.com/server/mcp-registry%2Fai.bringyour%2Fbringyour?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6df7afa69ac72a2d…, first seen 2026-10-17, included at leaf 4317 of 48,283. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 21:37 UTC, the Bringyour MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 2 minutes.
Bringyour MCP server advertises 7 tools, including install_local_cli, list_products, list_targets, preview_build_setup, preview_move.
Point your MCP client at this streamable-http endpoint: https://bringyour.ai/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.