Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AssetFare USDC Bridge

Owner verified

REMOTE · API.ASSETFARE.DEV

Exact-amount top-two routing for six pilots; caller signs; AssetFare never signs or submits

0 this week 84 Trust /100

Last scanned (13 minutes ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3777 tokens (~343/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
Changelog

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.

  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 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.

  • 25 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “assetfare_v2_capabilities” rewrote its description, which is the text the model reads security
    • Server version: 1.21.3 → 1.21.6 functional
  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://api.assetfare.dev/mcp/bridge

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.assetfare.dev CN=YE2,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA384 6d89db84b64463bc05613ce0ff4224f5669
SANs: api.assetfare.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.assetfare.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
assetfare.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.assetfare.dev/mcp/bridge Verified 200
http (plaintext) http://api.assetfare.dev/mcp/bridge HTTPS enforced 301 https://api.assetfare.dev/mcp/bridge
MCP tools · 11 exposed · ~3,663 tokens

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 →

Tool Tokens
assetfare_manifest ~52

Read the Ed25519-signed release manifest and safety-bundle binding before preparing an action. Example: call this once to verify the current release and contract pins; it never creates state, signs, or submits.

Input schema present but exposes no named parameters.

NameTypeReqDescription
executionobjectyes–
release_commitstringyes–
safety_bundleobjectyes–
servicestringyes–
signatureobjectyes–

No examples provided.

assetfare_v2_capabilities ~125

Read the 65 curated public routes, live provider readiness, whole-route product classification, direct_route_summary, and continuation_v3 contracts before quoting. The offered routes comprise 3 core, 50 conditional, and 12 strategic/scarce routes; 35 additional researched routes are not public products. Example: call once before requesting an exact route quote, then confirm the fresh quote. Route classification never adds an execution gate. continuation_v3 separately binds execution selection, wallets, bounds, and mode. Read-only; creates no wallet login, session, or action.

Input schema present but exposes no named parameters.

NameTypeReqDescription
action_lifetimeobjectyes–
asset_endpointsarrayyes–
blocked_source_only_routesarrayyes–
caller_owned_agent_execution–yes–
chainsarrayyes–
continuation_v3objectyes–
currently_prepare_ready_routesinteger––
direct_route_summary–yes–
directed_conversion_routesnumberyes–
economic_guidance–––
execution_availabilityobject––
execution_implemented_routesnumber––
execution_ready_routesnumberyes–
phase_b_blocked_routesnumberyes–
public_api_enabledbooleanyes–
server_signingbooleanyes–
server_submissionbooleanyes–
source_only_asset_endpointsarrayyes–
source_only_routesarrayyes–
statusstringyes–
temporarily_unavailable_route_countinteger––
temporarily_unavailable_routesarray––
unsigned_route_plans_readynumberyes–

No examples provided.

assetfare_v2_prepare ~506

Return one deeply verified first unsigned bundle and caller-wallet handoff. Example: pass caller_approved=true, a one_shot approval_v3, and the quote-bound verification_context; multi-step routes reject one_shot. Economic guidance is advisory and adds no request field. Context is validated before the upstream request and never forwarded. AssetFare never signs or submits.

NameTypeReqDescription
amount_usdnumberyesRequested input value in USD, minimum 1. USD 1 is reachability/schema smoke only. A USD 50 competitive bucket was observed only for dated 2026-09-23 Solana USDC to Base USDC evidence and must not be…
approval_v3objectyesStrict one-shot approval copied from the exact unexpired selected quote; its bounds may only be strengthened.
caller_approvedbooleanyesLegacy caller assertion that MUST be supplied explicitly. It is not human-proof and is never auto-inserted; approval_v3 adds server-enforced quote binding.
event_signer_public––Solana CCTP only: caller-generated ephemeral public key. Keep the matching private key client-side and use it to co-sign the returned unsigned event-account transaction; never send the private key.
from_chainstringyesSource chain for the v2 route. Polygon, Optimism, Ethereum, HyperEVM, X Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea, Aptos, Unichain, and Ink are source-only and cannot be used as t…
from_tokenstringyesInput token symbol on from_chain. The chain-token pair must appear in current v2 capabilities.
to_chainstringyesDestination chain for the v2 route: Solana, Base, Arbitrum, or Robinhood Chain. Source-only chains are not destinations.
to_tokenstringyesOutput token symbol on to_chain. The chain-token pair must appear in current v2 capabilities.
verification_contextobjectyesStrict caller-held one-shot context copied from the selected quote, approval and public wallets. It is verified before prepare and never forwarded upstream.
walletsobjectyesMap each chain needed by this route to the caller's public wallet address. Include public addresses only; never private keys or seed phrases.
NameTypeReqDescription
action_verificationobjectyesFail-closed semantic and approval-bound verification result; it never authorizes a signature by itself.
bundleobjectyesExact Core bundle whose payload_sha256 remains scoped only to this nested object.
caller_wallet_handoffobjectyesFresh self-verifying EIP-1193 or Solana Wallet Standard handoff. The caller still simulates, confirms, signs and submits.
local_execution_gateobjectyesRemote verification is not signing authority. Recompute locally and require verified_for_signing after fresh wallet simulation.
semantic_verificationbooleanyesTrue only after full decoded action, intent, receipt, payload and caller-bound verification.

No examples provided.

assetfare_v2_quote ~353

Get one fresh AssetFare quote with amount-specific economic_guidance, direct_route_summary, continuation_v3, and unsigned_prepare_requirements. Example: quote Solana USDC to Base USDC. price_recommended_for_amount is advisory; compare alternatives when price matters, but no economic acknowledgement field is required. The quote remains an unranked_candidate until separate explicit approval selects one mode. The adapter validates hashes, path, bounds, and TTL and never creates approval, prepares, signs, or submits.

NameTypeReqDescription
amount_usdnumberyesRequested input value in USD, minimum 1. USD 1 is reachability/schema smoke only. A USD 50 competitive bucket was observed only for dated 2026-09-23 Solana USDC to Base USDC evidence and must not be…
from_chainstringyesSource chain for the v2 route. Polygon, Optimism, Ethereum, HyperEVM, X Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea, Aptos, Unichain, and Ink are source-only and cannot be used as t…
from_tokenstringyesInput token symbol on from_chain. The chain-token pair must appear in current v2 capabilities.
to_chainstringyesDestination chain for the v2 route: Solana, Base, Arbitrum, or Robinhood Chain. Source-only chains are not destinations.
to_tokenstringyesOutput token symbol on to_chain. The chain-token pair must appear in current v2 capabilities.
NameTypeReqDescription
as_ofstringyes–
caller_action_plan_handoffobjectyes–
continuation_v3objectyes–
cost_summary–yes–
direct_route_summaryobjectyes–
economic_guidance–yes–
etaobjectyes–
executionobjectyes–
intentobjectyes–
offerobjectyes–
quote_idstringyes–
riskobjectyes–
routeobjectyes–
statusstringyes–
ttl_secondsintegeryes–

No examples provided.

assetfare_v2_quote_selected_candidate ~462

Reuse the chosen exact request-time quote while valid; after expiry refresh only that candidate at the same amount and never reselect. Example: pass candidate_id and the selection receipt hash. An AssetFare result requires a caller-local proof check and fresh wallet simulation before verified_for_signing; remote verification is not signing authority. An external result is only its provider handoff and has no AssetFare transaction-verification claim. Never prepares, signs, submits, or grants transaction authority.

NameTypeReqDescription
amount_usdnumberyesRequested input value in USD, minimum 1. USD 1 is reachability/schema smoke only. A USD 50 competitive bucket was observed only for dated 2026-09-23 Solana USDC to Base USDC evidence and must not be…
candidate_idstringyesExact candidate_id returned by assetfare_v2_route_selection; it is never chosen automatically.
from_chainstringyesSource chain for the v2 route. Polygon, Optimism, Ethereum, HyperEVM, X Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea, Aptos, Unichain, and Ink are source-only and cannot be used as t…
from_tokenstringyesInput token symbol on from_chain. The chain-token pair must appear in current v2 capabilities.
max_eta_secondsinteger–Optional stricter maximum ETA in seconds; it cannot exceed 60 or the selected profile limit.
profilestring–Time policy: fast (30s), balanced (60s default), or explicit economy (60s). Every recommendation profile has an absolute 60-second ceiling.
selection_receipt_sha256stringyesExact selection_receipt.sha256 returned with the fresh shortlist.
to_chainstringyesDestination chain for the v2 route: Solana, Base, Arbitrum, or Robinhood Chain. Source-only chains are not destinations.
to_tokenstringyesOutput token symbol on to_chain. The chain-token pair must appear in current v2 capabilities.
NameTypeReqDescription
choice_bindingobjectyes–
execution_handoffobjectyes–
selected_candidateobjectyes–
selection_quote_sourcestringyes–
server_signingbooleanyes–
server_submissionbooleanyes–
statusstringyes–
versionstringyes–

No examples provided.

assetfare_v2_route_selection ~442

Quote the recent top two plus the best AssetFare graph at the exact amount; return up to two all-in choices labeled assetfare_verified_unsigned or external_provider_handoff. AssetFare cost, ETA and rank are always present; a recent winning range needs two supporting higher buckets and disappears on conflict. Example: compare Solana USDC to Base USDC at USD 347.25 with balanced (60s). Fast is 30s; balanced and explicit economy are 60s. The 60-second ceiling is absolute for recommendations; slower routes are reference-only. Never approves, prepares, signs, or submits.

NameTypeReqDescription
amount_usdnumberyesRequested input value in USD, minimum 1. USD 1 is reachability/schema smoke only. A USD 50 competitive bucket was observed only for dated 2026-09-23 Solana USDC to Base USDC evidence and must not be…
from_chainstringyesSource chain for the v2 route. Polygon, Optimism, Ethereum, HyperEVM, X Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea, Aptos, Unichain, and Ink are source-only and cannot be used as t…
from_tokenstringyesInput token symbol on from_chain. The chain-token pair must appear in current v2 capabilities.
max_eta_secondsinteger–Optional stricter maximum ETA in seconds; it cannot exceed 60 or the selected profile limit.
profilestring–Time policy: fast (30s), balanced (60s default), or explicit economy (60s). Every recommendation profile has an absolute 60-second ceiling.
to_chainstringyesDestination chain for the v2 route: Solana, Base, Arbitrum, or Robinhood Chain. Source-only chains are not destinations.
to_tokenstringyesOutput token symbol on to_chain. The chain-token pair must appear in current v2 capabilities.
NameTypeReqDescription
as_ofstringyes–
assetfare_amount_guidanceobjectyes–
assetfare_direct_reference–yes–
automatic_reselection_forbiddenbooleanyes–
coverageobjectyes–
exact_quote_failuresarrayyes–
expired_selection_refresh_scopestringyes–
fresh_requote_required_after_selectionbooleanyes–
intentobjectyes–
precompute_amounts_used_usdarrayyes–
precompute_latest_evidence_atstringyes–
precompute_used_for_shortlisting_onlybooleanyes–
public_api_changedbooleanyes–
recommendationsarrayyes–
reference_onlyarrayyes–
request_amount_quoted_exactlybooleanyes–
request_time_exact_quote_countintegeryes–
safetyobjectyes–
schema_versionstringyes–
selection_grants_execution_authoritybooleanyes–
selection_policyobjectyes–
selection_quote_expires_atstringyes–
selection_quote_reused_while_validbooleanyes–
selection_receiptobjectyes–
shadow_onlybooleanyes–
shortlisted_candidate_countnumberyes–
shortlisted_candidate_idsarrayyes–
statusstringyes–

No examples provided.

assetfare_v2_session_create ~645

Create one receipt-driven workflow. Example: pass caller_approved=true, a session approval_v3, its idempotency_key, a caller-local session token, and the quote-bound verification_context. Economic guidance is advisory and adds no request field. The adapter validates approval and context before the upstream request. Every returned action is deeply verified and receives a caller-wallet handoff. AssetFare never signs or submits.

NameTypeReqDescription
amount_usdnumberyesRequested input value in USD, minimum 1. USD 1 is reachability/schema smoke only. A USD 50 competitive bucket was observed only for dated 2026-09-23 Solana USDC to Base USDC evidence and must not be…
approval_v3objectyesStrict Core 2.4.1 session quote-bound selection from the exact unexpired quote. Required for every remote session flow.
caller_approvedbooleanyesLegacy caller assertion that MUST be supplied explicitly. It is not human-proof and is never auto-inserted; approval_v3 adds server-enforced quote binding.
event_signer_public––Solana CCTP only: caller-generated ephemeral public key. Keep the matching private key client-side and use it to co-sign the returned unsigned event-account transaction; never send the private key.
from_chainstringyesSource chain for the v2 route. Polygon, Optimism, Ethereum, HyperEVM, X Layer, Sei, Sonic, Monad, Avalanche, Cronos, Injective, Linea, Aptos, Unichain, and Ink are source-only and cannot be used as t…
from_tokenstringyesInput token symbol on from_chain. The chain-token pair must appear in current v2 capabilities.
idempotency_keystringyesCaller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation. Strict approval_v3 requests additionally enforce its ASCII k…
session_tokenstringyesSensitive caller-generated v2 session capability: at least 32 CSPRNG bytes encoded as 43-128 URL-safe base64 characters. Generate it locally; never log it or substitute a private key or legacy access…
to_chainstringyesDestination chain for the v2 route: Solana, Base, Arbitrum, or Robinhood Chain. Source-only chains are not destinations.
to_tokenstringyesOutput token symbol on to_chain. The chain-token pair must appear in current v2 capabilities.
verification_contextobjectyesStrict caller-held context copied from the selected quote and approval. It contains public intent/wallet data only, never the raw session token or a private key, and is required whenever a remote MCP…
walletsobjectyesMap each chain needed by this route to the caller's public wallet address. Include public addresses only; never private keys or seed phrases.
NameTypeReqDescription
action_availablebooleanyes–
current_action–yes–
quote_binding–yes–
server_signingbooleanyes–
server_submissionbooleanyes–
session_idstringyes–
signedbooleanyes–
statusstringyes–
submittedbooleanyes–

No examples provided.

assetfare_v2_session_get ~212

Read an existing v2 workflow without advancing it. Example: pass session_id, session_token, and the original verification_context after restart. The adapter deeply verifies any current_action and emits a self-verifying wallet handoff, or fails closed. Read-only; never signs or submits.

NameTypeReqDescription
session_idstringyesV2 workflow session UUID returned by assetfare_v2_session_create. Use only with assetfare_v2_session_* tools; do not pass a legacy session ID.
session_tokenstringyesSensitive caller-generated v2 session capability: at least 32 CSPRNG bytes encoded as 43-128 URL-safe base64 characters. Generate it locally; never log it or substitute a private key or legacy access…
verification_contextobjectyesStrict caller-held context copied from the selected quote and approval. It contains public intent/wallet data only, never the raw session token or a private key, and is required whenever a remote MCP…
NameTypeReqDescription
action_availablebooleanyes–
current_action–yes–
quote_binding–yes–
server_signingbooleanyes–
server_submissionbooleanyes–
session_idstringyes–
signedbooleanyes–
statusstringyes–
submittedbooleanyes–

No examples provided.

assetfare_v2_session_observe_output ~299

Record an already-produced bridge or destination output, then advance the workflow. Example: pass the output hash, a new idempotency key, and the original verification_context. Any next current_action is deeply verified and receives a wallet handoff. AssetFare never signs or submits.

NameTypeReqDescription
idempotency_keystringyesCaller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation. Strict approval_v3 requests additionally enforce its ASCII k…
session_idstringyesV2 workflow session UUID returned by assetfare_v2_session_create. Use only with assetfare_v2_session_* tools; do not pass a legacy session ID.
session_tokenstringyesSensitive caller-generated v2 session capability: at least 32 CSPRNG bytes encoded as 43-128 URL-safe base64 characters. Generate it locally; never log it or substitute a private key or legacy access…
transaction_hashstring–Optional bridge or destination transaction hash already produced outside AssetFare. Omit only when the provider output can be observed without a hash.
verification_contextobjectyesStrict caller-held context copied from the selected quote and approval. It contains public intent/wallet data only, never the raw session token or a private key, and is required whenever a remote MCP…
NameTypeReqDescription
action_availablebooleanyes–
current_action–yes–
quote_binding–yes–
server_signingbooleanyes–
server_submissionbooleanyes–
session_idstringyes–
signedbooleanyes–
statusstringyes–
submittedbooleanyes–

No examples provided.

assetfare_v2_session_observe_source ~300

Record source hashes the caller already signed and submitted, then advance the workflow. Example: pass one finalized source hash, a new idempotency key, and the original verification_context. Any next current_action is deeply verified and receives a wallet handoff. AssetFare never signs or submits.

NameTypeReqDescription
idempotency_keystringyesCaller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation. Strict approval_v3 requests additionally enforce its ASCII k…
session_idstringyesV2 workflow session UUID returned by assetfare_v2_session_create. Use only with assetfare_v2_session_* tools; do not pass a legacy session ID.
session_tokenstringyesSensitive caller-generated v2 session capability: at least 32 CSPRNG bytes encoded as 43-128 URL-safe base64 characters. Generate it locally; never log it or substitute a private key or legacy access…
transaction_hashesarrayyesOne to eight hashes for source transactions the caller already signed and submitted. Do not provide unsigned payloads or destination hashes.
verification_contextobjectyesStrict caller-held context copied from the selected quote and approval. It contains public intent/wallet data only, never the raw session token or a private key, and is required whenever a remote MCP…
NameTypeReqDescription
action_availablebooleanyes–
current_action–yes–
quote_binding–yes–
server_signingbooleanyes–
server_submissionbooleanyes–
session_idstringyes–
signedbooleanyes–
statusstringyes–
submittedbooleanyes–

No examples provided.

assetfare_v2_session_refresh_action ~267

Refresh an expired action only while it remains unsubmitted. Example: pass the existing session, a new idempotency key, and the original verification_context. The refreshed action is deeply verified and receives a wallet handoff. Never refresh a submitted step; AssetFare never signs or submits.

NameTypeReqDescription
idempotency_keystringyesCaller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation. Strict approval_v3 requests additionally enforce its ASCII k…
session_idstringyesV2 workflow session UUID returned by assetfare_v2_session_create. Use only with assetfare_v2_session_* tools; do not pass a legacy session ID.
session_tokenstringyesSensitive caller-generated v2 session capability: at least 32 CSPRNG bytes encoded as 43-128 URL-safe base64 characters. Generate it locally; never log it or substitute a private key or legacy access…
verification_contextobjectyesStrict caller-held context copied from the selected quote and approval. It contains public intent/wallet data only, never the raw session token or a private key, and is required whenever a remote MCP…
NameTypeReqDescription
action_availablebooleanyes–
current_action–yes–
quote_binding–yes–
server_signingbooleanyes–
server_submissionbooleanyes–
session_idstringyes–
signedbooleanyes–
statusstringyes–
submittedbooleanyes–

No examples provided.

Install

How do I install the AssetFare USDC Bridge MCP server?

AssetFare USDC Bridge is a hosted endpoint at https://api.assetfare.dev/mcp/bridge, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.assetfare.dev

# add to Claude Code
claude mcp add --transport http assetfare-assetfare-bridge 'https://api.assetfare.dev/mcp/bridge'
Common questions

What is the AssetFare USDC Bridge MCP server?

AssetFare USDC Bridge is an MCP server listed in the public MCP registry as io.github.assetfare/assetfare-bridge. Exact-amount top-two routing for six pilots; caller signs; AssetFare never signs or submits. This page covers its hosted endpoint (https://api.assetfare.dev/mcp/bridge). Its publisher has verified ownership with us.

Is the AssetFare USDC Bridge MCP server safe to use?

AssetFare USDC Bridge scores 84 out of 100 on VerifyMCP. 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 AssetFare USDC Bridge MCP server expose?

AssetFare USDC Bridge exposes 11 tools: assetfare_manifest, assetfare_v2_capabilities, assetfare_v2_route_selection, assetfare_v2_quote_selected_candidate, assetfare_v2_quote, and 6 more. Their descriptions and schemas cost roughly 3,663 tokens of context every time the server is loaded.

Does the AssetFare USDC Bridge MCP server require authentication?

No. We connected to AssetFare USDC Bridge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AssetFare USDC Bridge MCP server still maintained?

AssetFare USDC Bridge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.