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.
ENDPOINT 1
https://api.assetfare.dev/mcp
MCP server metadata
- Name
- AssetFare
- Version
- 1.15.2
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_manifestRead the Ed25519-signed release manifest and safety-bundle binding before preparing an action.
Inferred read-onlyassetfare_v2_capabilitiesRead the 54 active routes, 44 economically inactive routes, live availability, route-specific guidance, direct_route_summary, and continuation_v3 contracts before quoting.
Inferred read-onlyassetfare_v2_quoteGet one fresh AssetFare quote with route-specific economic_guidance, direct_route_summary, and continuation_v3.
Inferred read-onlyassetfare_v2_prepareReturn one deeply verified first unsigned bundle plus a self-verifying caller-wallet handoff.
Inferred read-onlyassetfare_v2_session_observe_sourceRecord source hashes the caller already signed and submitted, then advance the workflow.
Inferred read-onlyassetfare_v2_session_observe_outputRecord an already-produced bridge or destination output, then advance the workflow.
Inferred read-onlyassetfare_v2_session_refresh_actionRefresh an expired action only while it remains unsubmitted.
Inferred read-onlyCONNECT 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
MCP server metadata
- Name
- AssetFare
- Version
- 1.15.2
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_statusRead legacy v1 compatibility status and original-corridor safety gates.
Inferred read-onlyassetfare_manifestRead the Ed25519-signed release manifest and safety-bundle binding before preparing an action.
Inferred read-onlyassetfare_quoteLegacy v1 original-corridor quote: get Solana SOL to Base or Arbitrum ETH pricing.
Inferred read-onlyassetfare_start_wallet_authCreate a short-lived, non-transactional Solana signMessage challenge for the legacy v1 workflow.
Potential side effectsassetfare_finish_wallet_authVerify the caller's signature over the exact legacy login challenge and return a sensitive wallet-bound access token.
Inferred read-onlyassetfare_create_sessionLock one fresh legacy assetfare_quote into a wallet-bound v1 execution session.
Inferred read-onlyassetfare_read_sessionRead a legacy v1 session summary, workflow state, receipt, or current unsigned action.
Inferred read-onlyassetfare_prepare_source_actionPrepare the bounded unsigned Solana source action for the current legacy v1 session step.
Inferred read-onlyassetfare_verify_source_receiptVerify a finalized Solana source signature already submitted by the caller and advance the legacy v1 workflow.
Inferred read-onlyassetfare_prepare_cctp_actionPrepare the unsigned CCTP burn for the current legacy v1 session using a caller-owned event signer public key.
Inferred read-onlyassetfare_observe_cctpVerify Circle attestation and the forwarded Base or Arbitrum USDC mint for a caller-submitted legacy v1 burn, then advance the session record.
Inferred read-onlyassetfare_prepare_destination_actionPrepare the exact-cap permit and unsigned ERC-4337 destination settlement plan for the current legacy v1 session.
Inferred read-onlyassetfare_observe_destinationVerify an already-submitted destination UserOperation receipt and finalize the legacy v1 workflow record.
Inferred read-onlyCONNECT 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.
assetfare.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.