Model Context Protocol (MCP) server for freee API integration
AssetFare USDC Bridge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Non-custodial USDC bridge and cross-chain swap quotes: Solana to Base; unsigned, never signs/submits
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http assetfare-usdc-bridge-mcp https://api.assetfare.dev/mcp/bridge
# 2 — ask your agent for something these tools do
# assetfare_status, assetfare_manifest, assetfare_v2_capabilities and 19 more
AssetFare USDC Bridge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http assetfare-usdc-bridge-mcp https://api.assetfare.dev/mcp/bridgeReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read legacy v1 compatibility status and original-corridor safety gates. Use assetfare_v2_capabilities for the primary six-chain source quote and execution surface.
No parameter schema on file.
Read the Ed25519-signed capability, contract, release, and mainnet-evidence manifest.
No parameter schema on file.
Non-custodial cross-chain bridge and swap capabilities: Solana SOL to Base USDC and 75 other routes across six chains and eleven source endpoints, with Polygon/Optimism native-USDC source-only routes. Read live availability, the fee model (AssetFare service fee 1bp; Circle/provider/network fees additional), and the no-sign/no-submit boundary before quoting.
No parameter schema on file.
Get one fresh AssetFare cross-chain bridge/swap quote for any of 76 routes, including Solana SOL to Base USDC, Solana USDC to Base USDC, and Optimism USDC to Base USDC. AssetFare service fee 1bp; Circle/provider/network fees additional; judge the route by the quote's total token-path cost and live availability, not the 1bp alone. Returns a caller-approved unsigned-action handoff; never signs, subm
No parameter schema on file.
Local-only: generate one caller-owned high-entropy session capability token (>=256-bit CSPRNG, url-safe, 43-128 chars). Makes NO network call. Store it as a SENSITIVE capability (never a private key); pass it into assetfare_v2_session_create and every session read/observe/refresh.
No parameter schema on file.
Explicit caller-approved one-shot: POST /v2/prepare for a route the live quote reports available. Solana-CCTP routes require event_signer_public: generate a fresh ephemeral Solana keypair locally, pass only its public key, keep its private key client-side, and co-sign the returned unsigned event-account transaction. Never auto-called; AssetFare never signs or submits.
No parameter schema on file.
Explicit caller-approved receipt-driven /v2/session create. Solana-CCTP routes require event_signer_public from a fresh caller-generated ephemeral keypair; only its public key is sent and the private key stays client-side. Also requires a caller-generated session capability token and exact public wallet map. Never auto-chains, signs, or submits.
No parameter schema on file.
Read a v2 session's current workflow state and current unsigned action. Requires the caller's session capability token. Read-only; never signs or submits.
No parameter schema on file.
Observe the caller's already-submitted source transaction hashes for a v2 session and advance the workflow. Requires the caller's session capability token. Never submits a transaction.
No parameter schema on file.
Observe the caller's already-produced bridge/destination output for a v2 session and advance the workflow. Requires the caller's session capability token. Never submits a transaction.
No parameter schema on file.
Replace an expired unsubmitted v2 session action with a fresh quote-bound unsigned action. Requires the caller's session capability token. Never signs or submits.
No parameter schema on file.
Legacy v1 original-corridor quote for Solana SOL to Base or Arbitrum ETH. Use only with the legacy wallet-auth/session workflow; prefer assetfare_v2_quote for new evaluations.
No parameter schema on file.
Create a non-transactional Solana signMessage challenge. Requires caller approval because it creates a short-lived login challenge; it cannot move funds.
No parameter schema on file.
Verify a wallet signature over the exact challenge message and return a wallet-bound access token. Requires caller approval; the returned token is sensitive.
No parameter schema on file.
Lock a fresh quote into a wallet-bound execution session. This creates no transaction, but reserves the caller's one active session slot.
No parameter schema on file.
Read a wallet-bound session, workflow, receipt, or current unsigned action. Read-only.
No parameter schema on file.
Prepare a bounded unsigned Solana source action. Requires caller approval; it never signs or submits.
No parameter schema on file.
Verify a caller-submitted finalized Solana source signature and advance the workflow. Requires caller approval; it never submits a transaction.
No parameter schema on file.
Prepare an unsigned CCTP burn action using a caller-generated event signer public key. Requires caller approval; it never signs or submits.
No parameter schema on file.
Verify Circle attestation and the forwarded Base or Arbitrum USDC mint for an already-submitted burn. Read-only on chain, but advances the session record.
No parameter schema on file.
Prepare the exact-cap permit and unsigned ERC-4337 destination settlement plan. Requires caller approval; it never signs or submits.
No parameter schema on file.
Verify an already-submitted destination UserOperation receipt and finalize the workflow. Requires caller approval; it never submits a transaction.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AssetFare USDC Bridge or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.21.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish AssetFare USDC Bridge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.