Wealthville Integrati… vs Galactic Bridge | AllMCPs
Side-by-Side Model Context Protocol Comparison
Wealthville Integrations vs Galactic Bridge
In-depth architectural comparison of the Wealthville Integrations and Galactic Bridge MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Wealthville Integrations
Finance & Fintech · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Galactic Bridge
Finance & Fintech · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Wealthville Integrations if you need specialized Finance & Fintech tools running via a local process. Choose Galactic Bridge if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Wealthville Integrations when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Pool scores from 0 to 100, Enter, Hold, or Exit verdicts, Solana and EVM pool coverage.
Solana + EVM liquidity-pool scores for AI agents: Enter/Hold/Exit verdicts and a composite 0–100 Wealthville Score, plus a live, immutable, miss-inclusive track record. 4 read-only tools (pool score, top pools, track record, signals feed). In the official MCP Registry. npx @wealthville/mcp-server
Find LayerZero OFT bridge routes by contract address across 14 EVM networks.
Wealthville Integrations is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Galactic Bridge belongs to Finance & Fintech using local stdio subprocess. Select Wealthville Integrations when you need capabilities focused on finance & fintech and Galactic Bridge when you require tools for finance & fintech.
Given a token address, every network it exists on and its OFT contract on each.
find_bridge_route
Resolves a route between two networks: OFT contract, whether the direction is enabled right now, the fee, and — with `amount` + `recipient` — a ready-to-sign transaction (plus an ERC-20 approval when the token bridges through a separate adapter).