← Registry

API Tools

assetfare.dev

Provides tools to read AssetFare release manifests, capabilities, and routes, then generate verified quotes, prepare unsigned transaction bundles, and create receipt-driven workflows for asset routing.

2 endpoints22 known toolsFirst detected October 6, 2026Last detected October 7, 2026

ENDPOINT 1

https://api.assetfare.dev/mcp

No auth detected

MCP server metadata

Name
AssetFare
Version
1.15.2
Capabilities
tools.listChanged
Server instructions

Current AssetFare v2 endpoint: 54 economically active non-custodial routes; 44 measured routes are inactive. Start with assetfare_v2_capabilities, then quote. Prepare only after explicit caller approval and public wallets; choose one-shot prepare or session mode, never both. Session capabilities are generated client-side. AssetFare never receives private keys, signs, or submits. Legacy tools live at https://api.assetfare.dev/mcp/legacy.

Known tools 9

assetfare_manifest

Read the Ed25519-signed release manifest and safety-bundle binding before preparing an action.

Inferred read-only
assetfare_v2_capabilities

Read the 54 active routes, 44 economically inactive routes, live availability, route-specific guidance, direct_route_summary, and continuation_v3 contracts before quoting.

Inferred read-only
assetfare_v2_quote

Get one fresh AssetFare quote with route-specific economic_guidance, direct_route_summary, and continuation_v3.

Inferred read-only
assetfare_v2_prepare

Return one deeply verified first unsigned bundle plus a self-verifying caller-wallet handoff.

Inferred read-only
assetfare_v2_session_create

Create one receipt-driven workflow.

Potential side effects
assetfare_v2_session_get

Read an existing v2 workflow without advancing it.

Inferred read-only
assetfare_v2_session_observe_source

Record source hashes the caller already signed and submitted, then advance the workflow.

Inferred read-only
assetfare_v2_session_observe_output

Record an already-produced bridge or destination output, then advance the workflow.

Inferred read-only
assetfare_v2_session_refresh_action

Refresh an expired action only while it remains unsubmitted.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.assetfare]
url = "https://api.assetfare.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: assetfare
Remote MCP URL: https://api.assetfare.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "assetfare": {
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "assetfare",
  "transport": "streamable-http",
  "url": "https://api.assetfare.dev/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://api.assetfare.dev/mcp/legacy

No auth detected

MCP server metadata

Name
AssetFare
Version
1.15.2
Capabilities
tools.listChangedresources.listChanged
Server instructions

Legacy compatibility endpoint for the original Solana SOL to Base/Arbitrum ETH workflow. Use only its unversioned tools. It returns unsigned actions and never receives private keys, signs, or submits. New integrations must use https://api.assetfare.dev/mcp.

Known tools 13

assetfare_status

Read legacy v1 compatibility status and original-corridor safety gates.

Inferred read-only
assetfare_manifest

Read the Ed25519-signed release manifest and safety-bundle binding before preparing an action.

Inferred read-only
assetfare_quote

Legacy v1 original-corridor quote: get Solana SOL to Base or Arbitrum ETH pricing.

Inferred read-only
assetfare_start_wallet_auth

Create a short-lived, non-transactional Solana signMessage challenge for the legacy v1 workflow.

Potential side effects
assetfare_finish_wallet_auth

Verify the caller's signature over the exact legacy login challenge and return a sensitive wallet-bound access token.

Inferred read-only
assetfare_create_session

Lock one fresh legacy assetfare_quote into a wallet-bound v1 execution session.

Inferred read-only
assetfare_read_session

Read a legacy v1 session summary, workflow state, receipt, or current unsigned action.

Inferred read-only
assetfare_prepare_source_action

Prepare the bounded unsigned Solana source action for the current legacy v1 session step.

Inferred read-only
assetfare_verify_source_receipt

Verify a finalized Solana source signature already submitted by the caller and advance the legacy v1 workflow.

Inferred read-only
assetfare_prepare_cctp_action

Prepare the unsigned CCTP burn for the current legacy v1 session using a caller-owned event signer public key.

Inferred read-only
assetfare_observe_cctp

Verify Circle attestation and the forwarded Base or Arbitrum USDC mint for a caller-submitted legacy v1 burn, then advance the session record.

Inferred read-only
assetfare_prepare_destination_action

Prepare the exact-cap permit and unsigned ERC-4337 destination settlement plan for the current legacy v1 session.

Inferred read-only
assetfare_observe_destination

Verify an already-submitted destination UserOperation receipt and finalize the legacy v1 workflow record.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.assetfare]
url = "https://api.assetfare.dev/mcp/legacy"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp/legacy"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: assetfare
Remote MCP URL: https://api.assetfare.dev/mcp/legacy

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "assetfare": {
      "url": "https://api.assetfare.dev/mcp/legacy"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp/legacy"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "assetfare",
  "transport": "streamable-http",
  "url": "https://api.assetfare.dev/mcp/legacy"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for assetfare.dev was fetched 2026-10-08T12:18:55.452Z.

Trust status Neutral

assetfare.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.