Galactic Bridge
NPM · GALACTIC-BRIDGE-MCP
Find LayerZero OFT bridge routes by contract address across 14 EVM networks.
Available components
Last scanned (21 hours ago)
Scores higher than 65% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 391 tokens (~130/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 26 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
- 23 Oct 26 0
- Security disclosure: fail → unverified ▼ 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 4 Nov 2026 · Analysed npm/galactic-bridge-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
find_bridge_route ~237
Resolve the bridge route for a token between two networks: the OFT contract, whether the direction is enabled right now, the fee, and — if amount and recipient are given — a ready-to-sign transaction (plus an ERC-20 approval transaction when the token bridges through a separate adapter). This tool NEVER signs or sends; it returns transactions for a human or wallet to review and sign.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Human-readable amount to bridge, e.g. "12.5". Required to build a transaction. |
| decimals | integer | – | Token decimals. Read automatically if omitted; pass explicitly to be certain. |
| fromChain | string | yes | Source network key (e.g. "bsc"). See list_supported_networks. |
| oftContract | string | – | Optional: the OFT contract address, if you already know it (skips discovery). |
| recipient | string | – | Recipient address on the destination network (also the refund address). Required to build a transaction. |
| toChain | string | yes | Destination network key (e.g. "arc"). |
| token | string | yes | Token contract address (0x…). |
No output schema declared.
No examples provided.
list_supported_networks ~51
List the EVM networks Galactic Bridge supports, with their chain key, chainId, LayerZero endpoint id (eid) and native gas symbol. Use the `key` values when calling the other tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_token_networks ~103
Given a token contract address, find every supported network the token exists on and its OFT bridge contract on each. Useful to discover where a token can be bridged from and to before resolving a specific route.
| Name | Type | Req | Description |
|---|---|---|---|
| fromChain | string | – | Optional network key to start the scan from (e.g. "bsc"). Auto-detected if omitted. |
| token | string | yes | The token contract address (0x…). Works on any of the supported networks. |
No output schema declared.
No examples provided.
How do I install the Galactic Bridge MCP server?
Galactic Bridge runs locally as an npm package, launched with npx -y galactic-bridge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · galactic-bridge-mcp
claude mcp add mckellen-eth-galactic-bridge-mcp -- npx -y galactic-bridge-mcp
What is the Galactic Bridge MCP server?
Galactic Bridge is an MCP server listed in the public MCP registry as io.github.mckellen-eth/galactic-bridge-mcp. Find LayerZero OFT bridge routes by contract address across 14 EVM networks. This page covers its npm package (galactic-bridge-mcp).
Is the Galactic Bridge MCP server safe to use?
Galactic Bridge scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 Galactic Bridge MCP server expose?
Galactic Bridge exposes 3 tools: list_supported_networks, scan_token_networks, find_bridge_route. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Is the Galactic Bridge MCP server still maintained?
Galactic Bridge is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Galactic Bridge MCP server under?
Galactic Bridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.