mcpbeat Sign in

Multi-Bridge MCP Server

answering

Multi-Bridge is answering right now. Last checked moments ago.

Cross-chain pathfinder and bridge routing optimization using Li.Fi.

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
109 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check Multi-Bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add multi-bridge --transport sse https://multi-bridge-mcp.vercel.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://multi-bridge-mcp.vercel.app/api/mcp
~/.codex/config.toml
[mcp_servers.multi-bridge]
url = "https://multi-bridge-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "multi-bridge": {
      "url": "https://multi-bridge-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "multi-bridge": {
      "type": "sse",
      "url": "https://multi-bridge-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://multi-bridge-mcp.vercel.app/api/mcp sse needs auth 112 ms 0 min ago

Alternatives to Multi-Bridge

same job, measured the same way
LogisticFlow
by evozim

Logistics path finder and supply chain route optimizer.

1 tools answering
Routing24
by routing24

Route optimization for delivery fleets: plan, edit, and re-optimize multi-stop routes by prompt.

answering
Relay
by reservoirprotocol

Cross-chain bridge and swap quotes, fee estimation, and transaction tracking via Relay Protocol.

117 installs/wk local only
Relay
by relayprotocol

Cross-chain bridge and swap quotes, fee estimation, and transaction tracking via Relay Protocol.

local only
Dex Data MCP
by donnywin85

Multi-chain DEX prices, liquidity, routing and slippage. Free tier, no API key.

local only
MyRouteOnline
by myrouteonline

Multi-stop route optimization, navigation links, and email delivery. Powered by MyRouteOnline.

4 tools answering
B
BridgePilot — cross-chain route quotes
by ert1981

Best cross-chain route via LI.FI + Across with net USD value. Non-custodial, x402-paid.

1 tools answering
three.ws Brain
by nirholas

List LLM providers and run chat completions through the three.ws multi-provider router.

118 installs/wk local only

Multi-Bridge — questions

Answers built from our own checks of this server.

Why is there no tool list for Multi-Bridge?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Multi-Bridge working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 109 ms. The bar chart above shows every period we have measured.
How do I connect Multi-Bridge?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Multi-Bridge need an API key?
Yes. Every time we knock, Multi-Bridge answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Multi-Bridge?
It answers our handshake in 109 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.