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

REMOTE · API.ASSETFARE.DEV · SCANNED SEP 20

Six-chain source quotes incl. Polygon/Optimism USDC; AssetFare never signs or submits.

74 Trust /100
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 Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1919 tokens (~83/item across 23 items; 22 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 24 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
Install

How do I install the AssetFare MCP server?

AssetFare is a hosted endpoint at https://api.assetfare.dev/mcp, 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 odaiin-assetfare 'https://api.assetfare.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "odaiin-assetfare": {
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "odaiin-assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.odaiin-assetfare]
url = "https://api.assetfare.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "odaiin-assetfare": {
      "type": "remote",
      "url": "https://api.assetfare.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add odaiin-assetfare --url 'https://api.assetfare.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  odaiin-assetfare:
    url: "https://api.assetfare.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "odaiin-assetfare": {
      "Transport": "http",
      "Url": "https://api.assetfare.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add odaiin-assetfare -t streamable-http -u 'https://api.assetfare.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "odaiin-assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 20 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “assetfare_status” rewrote its description, which is the text the model reads security
    • Tool “assetfare_v2_capabilities” rewrote its description, which is the text the model reads security
    • Tool “assetfare_v2_quote” rewrote its description, which is the text the model reads security
    • Schema quality: 65 → 83 functional
    • Server version: 0.4.1 → 0.4.3 functional
    • New tool “assetfare_v2_new_session_capability” functional
    • New tool “assetfare_v2_prepare” functional
    • New tool “assetfare_v2_session_create” functional
    • New tool “assetfare_v2_session_get” functional
    • New tool “assetfare_v2_session_observe_output” functional
    • New tool “assetfare_v2_session_observe_source” functional
    • New tool “assetfare_v2_session_refresh_action” functional
  • 18 Sept 26 +1

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

  • 17 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “assetfare_quote” rewrote its description, which is the text the model reads security
    • Tool “assetfare_status” rewrote its description, which is the text the model reads security
    • Schema quality: 59 → 65 functional
    • Server version: 0.4.0 → 0.4.1 functional
    • Server version: 0.2.0 → 0.4.0 functional
    • New tool “assetfare_v2_capabilities” functional
    • New tool “assetfare_v2_quote” functional
  • 16 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Sept 26 0
    • Tool “assetfare_observe_cctp” rewrote its description, which is the text the model reads security
    • Tool “assetfare_quote” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 functional
    • Server version: 0.1.0 → 0.2.0 functional
    • “assetfare_quote” added an optional parameter “destination_chain” cosmetic
  • 14 Sept 26 71

    First indexed and scored.

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 20 Sept 2026 · Probed https://api.assetfare.dev/mcp

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=86400
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 Verified 200
http (plaintext) http://api.assetfare.dev/mcp HTTPS enforced 301 https://api.assetfare.dev/mcp
MCP tools · 22 exposed · ~1,652 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_create_session ~78

Lock a fresh quote into a wallet-bound execution session. This creates no transaction, but reserves the caller's one active session slot.

NameTypeReqDescription
access_tokenstringyes
destination_walletstringyes
idempotency_keystringyes
quote_idstringyes
source_walletstringyes

No output schema declared.

No examples provided.

assetfare_finish_wallet_auth ~69

Verify a wallet signature over the exact challenge message and return a wallet-bound access token. Requires caller approval; the returned token is sensitive.

NameTypeReqDescription
challenge_idstringyes
signaturestringyes
source_walletstringyes
terms_versionstringyes

No output schema declared.

No examples provided.

assetfare_manifest ~29

Read the Ed25519-signed capability, contract, release, and mainnet-evidence manifest.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

assetfare_observe_cctp ~79

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.

NameTypeReqDescription
access_tokenstringyes
burn_signaturestringyes
idempotency_keystringyes
session_idstringyes

No output schema declared.

No examples provided.

assetfare_observe_destination ~69

Verify an already-submitted destination UserOperation receipt and finalize the workflow. Requires caller approval; it never submits a transaction.

NameTypeReqDescription
access_tokenstringyes
idempotency_keystringyes
session_idstringyes
transaction_hashstringyes

No output schema declared.

No examples provided.

assetfare_prepare_cctp_action ~75

Prepare an unsigned CCTP burn action using a caller-generated event signer public key. Requires caller approval; it never signs or submits.

NameTypeReqDescription
access_tokenstringyes
event_signer_publicstringyes
idempotency_keystringyes
session_idstringyes

No output schema declared.

No examples provided.

assetfare_prepare_destination_action ~62

Prepare the exact-cap permit and unsigned ERC-4337 destination settlement plan. Requires caller approval; it never signs or submits.

NameTypeReqDescription
access_tokenstringyes
idempotency_keystringyes
session_idstringyes

No output schema declared.

No examples provided.

assetfare_prepare_source_action ~46

Prepare a bounded unsigned Solana source action. Requires caller approval; it never signs or submits.

NameTypeReqDescription
access_tokenstringyes
session_idstringyes

No output schema declared.

No examples provided.

assetfare_quote ~66

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.

NameTypeReqDescription
amount_usdintegeryes
destination_chainstring

No output schema declared.

No examples provided.

assetfare_read_session ~51

Read a wallet-bound session, workflow, receipt, or current unsigned action. Read-only.

NameTypeReqDescription
access_tokenstringyes
session_idstringyes
viewstring

No output schema declared.

No examples provided.

assetfare_start_wallet_auth ~48

Create a non-transactional Solana signMessage challenge. Requires caller approval because it creates a short-lived login challenge; it cannot move funds.

NameTypeReqDescription
source_walletstringyes

No output schema declared.

No examples provided.

assetfare_status ~41

Read legacy v1 compatibility status and original-corridor safety gates. Use assetfare_v2_capabilities for the primary six-chain source quote and execution surface.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

assetfare_v2_capabilities ~65

Primary current six-chain source discovery tool. Read the live eleven source endpoints, all 76 execution-ready directed routes, the four directional Polygon/Optimism native-USDC source-only routes, release status, and the no-sign/no-submit boundary before a v2 quote.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

assetfare_v2_new_session_capability ~80

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

assetfare_v2_prepare ~151

Explicit caller-approved one-shot: POST the fixed-origin /v2/prepare to obtain the fresh re-quoted bounded FIRST unsigned action bundle for any of the 76 execution-ready routes. Requires caller_approved:true and the route's exact public wallet map. Never auto-called from a quote; rejects any private key/seed/signed transaction. AssetFare never signs or submits.

NameTypeReqDescription
amount_usdnumberyes
caller_approvedbooleanyes
event_signer_public
from_chainstringyes
from_tokenstringyes
to_chainstringyes
to_tokenstringyes
walletsobjectyes

No output schema declared.

No examples provided.

assetfare_v2_quote ~120

Primary current quote-only tool. Return one fresh non-binding quote across Solana, Base, Arbitrum, Robinhood Chain, or Polygon/Optimism native-USDC source routes to Base/Arbitrum, pass through the caller action-plan handoff, and stop before authentication, session creation, action preparation, signing, or submission.

NameTypeReqDescription
amount_usdnumberyes
from_chainstringyes
from_tokenstringyes
to_chainstringyes
to_tokenstringyes

No output schema declared.

No examples provided.

assetfare_v2_session_create ~163

Explicit caller-approved: create one idempotent receipt-driven /v2/session for an execution-ready route and return its first unsigned action. Requires caller_approved:true, a caller-generated session capability token (X-AssetFare-Session-Token), and the route's exact public wallet map. Never auto-chains, signs, or submits.

NameTypeReqDescription
amount_usdnumberyes
caller_approvedbooleanyes
event_signer_public
from_chainstringyes
from_tokenstringyes
idempotency_keystringyes
session_tokenstringyes
to_chainstringyes
to_tokenstringyes
walletsobjectyes

No output schema declared.

No examples provided.

assetfare_v2_session_get ~58

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.

NameTypeReqDescription
session_idstringyes
session_tokenstringyes

No output schema declared.

No examples provided.

assetfare_v2_session_observe_output ~81

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.

NameTypeReqDescription
idempotency_keystringyes
session_idstringyes
session_tokenstringyes
transaction_hashstring

No output schema declared.

No examples provided.

assetfare_v2_session_observe_source ~82

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.

NameTypeReqDescription
idempotency_keystringyes
session_idstringyes
session_tokenstringyes
transaction_hashesarrayyes

No output schema declared.

No examples provided.

assetfare_v2_session_refresh_action ~69

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.

NameTypeReqDescription
idempotency_keystringyes
session_idstringyes
session_tokenstringyes

No output schema declared.

No examples provided.

assetfare_verify_source_receipt ~70

Verify a caller-submitted finalized Solana source signature and advance the workflow. Requires caller approval; it never submits a transaction.

NameTypeReqDescription
access_tokenstringyes
idempotency_keystringyes
session_idstringyes
signaturestringyes

No output schema declared.

No examples provided.

Common questions

What is the AssetFare MCP server?

AssetFare is an MCP server listed in the public MCP registry as io.github.odaiin/assetfare. Six-chain source quotes incl. Polygon/Optimism USDC; AssetFare never signs or submits. This page covers its hosted endpoint (https://api.assetfare.dev/mcp).

Is the AssetFare MCP server safe to use?

AssetFare scores 74 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 MCP server expose?

AssetFare exposes 22 tools: assetfare_status, assetfare_manifest, assetfare_v2_capabilities, assetfare_v2_quote, assetfare_v2_new_session_capability, and 17 more. Their descriptions and schemas cost roughly 1,652 tokens of context every time the server is loaded.

Does the AssetFare MCP server require authentication?

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

Is the AssetFare MCP server still maintained?

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