mcp-registry/io.github.br0ski777/bridge-routes · v1.0.0
Also listed as glama/br0ski777/bridge-routes-x402
As of 2026-10-23 19:46 UTC, the Br0ski777 Bridge Routes MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Best cross-chain bridge routes with fees, time, providers. LI.FI-powered. x402.
Point your MCP client at this streamable-http endpoint: https://bridge-routes.api.klymax402.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
1 of 1 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 →
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%2Fio.github.br0ski777%2Fbridge-routes/fixes
{
"name": "bridge_find_best_route",
"description": "Use this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON. POST variant of bridge_find_best_route -- same params passed as JSON body instead of query string.\n\n1. routes: array of bridge options ranked by best value\n2. bridgeProvider: which bridge protocol (Stargate, Across, Hop, Connext, etc.)\n3. estimatedTime: expected bridge completion time in seconds\n4. fee: total bridging fee in USD\n5. amountReceived: expected output amou",
"inputSchema": {
"type": "object",
"required": [
"fromChain",
"toChain",
"token",
"amount"
],
"properties": {
"token": {
"type": "string",
"description": "Token symbol to bridge (e.g. USDC, USDT, ETH, WETH)"
},
"amount": {
"type": "string",
"description": "Amount in smallest unit (e.g. 1000000 for 1 USDC with 6 decimals, 1000000000000000000 for 1 ETH)"
},
"toChain": {
"type": "string",
"description": "Destination chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche)"
},
"toToken": {
"type": "string",
"description": "Destination token symbol if different from source (optional, defaults to same as token)"
},
"fromChain": {
"type": "string",
"description": "Source chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche)"
}
}
},
"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/io.github.br0ski777/bridge-routes"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.br0ski777/bridge-routes"}) over MCP.
bridge_find_best_route ~370 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%2Fio.github.br0ski777%2Fbridge-routes?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Fbridge-routes?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Fbridge-routes.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.br0ski777%2Fbridge-routes.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.br0ski777%2Fbridge-routes?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:4255b05227f299fe…, first seen 2026-10-17, included at leaf 13190 of 77,676. Version history · verify what your client received.
Compare: 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-23 19:46 UTC, the Br0ski777 Bridge Routes MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Br0ski777 Bridge Routes MCP server advertises 1 tool, including bridge_find_best_route.
Point your MCP client at this streamable-http endpoint: https://bridge-routes.api.klymax402.com/mcp
Glimind scanned all 1 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.