assetfare-bridge
MCP serverEverything elseNon-custodial USDC bridge and cross-chain swap quotes: Solana to Base; unsigned, never signs/submits
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use assetfare-bridge
Install assetfare-bridge
The server’s own address, for the clients that take one directly. Or connect ahel onceand every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http assetfare-bridge 'https://api.assetfare.dev/mcp/bridge'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://api.assetfare.dev/mcp/bridgeAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=assetfare-bridge&config=eyJ1cmwiOiJodHRwczovL2FwaS5hc3NldGZhcmUuZGV2L21jcC9icmlkZ2UifQ==Open the link and Cursor adds the server at that address.
ChatGPT
https://api.assetfare.dev/mcp/bridgeIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add assetfare-bridge --url 'https://api.assetfare.dev/mcp/bridge'Run it once, then sign in with codex mcp login assetfare-bridge if the server asks for an account.
From the project's README
As published by odaiin/assetfare-mcp in README.md. This repository publishes several servers, so only the opening is shown here.
An MCP client/server wrapper for AssetFare's capped, non-custodial Solana SOL → Base ETH workflow.
Safety model
- AssetFare MCP never accepts a private key and never signs or submits a transaction.
- Read-only tools expose current status, signed manifest, and quotes.
- State-changing tools only create authentication/session records or prepare/verify unsigned workflow actions. MCP clients should require user approval for those calls.
- The caller independently verifies every returned unsigned action and signs/submits with its own wallets.
Remote endpoint
https://api.assetfare.dev/mcp
Official MCP Registry server: io.github.odaiin/assetfare.
Use Streamable HTTP. The endpoint has no server-side API key; wallet authentication happens through the AssetFare tools.
Local stdio
The repository also contains a stdio-compatible wrapper for self-hosting. The public Registry entry uses the remote Streamable HTTP endpoint; npm publication is intentionally deferred until a separate package-release review.
Trust material
Shortened here. Read the whole README on GitHub.
Advanced
- Delivery
- assetfare-bridge MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
io-github-odaiin-assetfare-bridge- Source
- github.com/odaiin/assetfare-mcp
- Hosted endpoint
https://api.assetfare.dev/mcp/bridge