Multi-Bridge vs io.github.persistenceOne/bridgekitty
Multi-Bridge is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.persistenceOne/bridgekitty is an MCP server published by persistenceOne. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.persistenceOne/bridgekitty | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.3.1 Downloads/month (npm): 229 Downloads/week (npm): 57 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Multi-Bridge | io.github.persistenceOne/bridgekitty |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (multi-bridge-mcp.vercel.app/api/mcp) | On your machine (@persistenceone/bridgekitty) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/persistenceone/bridgekitty |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Multi-Bridge
Cross-chain pathfinder and bridge routing optimization using Li.Fi.
io.github.persistenceOne/bridgekitty
Cross-chain bridge aggregator — compares LI.FI, deBridge, Relay, Across & more for best rates.
How to run each
Multi-Bridge As a remote MCP server
claude mcp add --transport sse multi-bridge https://multi-bridge-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
io.github.persistenceOne/bridgekitty As a local MCP server: npm package
claude mcp add --env "LIFI_API_KEY=<YOUR_LIFI_API_KEY>" --transport stdio bridgekitty -- npx -y @persistenceone/bridgekittyRequires: LIFI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Multi-Bridge publish no settings it asks for, so we do not compare settings.
What it can do: Multi-Bridge · What it can do: io.github.persistenceOne/bridgekitty · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.