# AssetFare (remote · api.assetfare.dev)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.assetfare.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/odaiin-assetfare/api.md), [page](https://verifymcp.io/servers/odaiin-assetfare/api)

## Channel facts

- Endpoint: `https://api.assetfare.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1919 tokens (~83/item across 23 items; 22 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http odaiin-assetfare 'https://api.assetfare.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "odaiin-assetfare": {
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "odaiin-assetfare": {
      "type": "http",
      "url": "https://api.assetfare.dev/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add odaiin-assetfare --url 'https://api.assetfare.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  odaiin-assetfare:
    url: "https://api.assetfare.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "odaiin-assetfare": {
      "Transport": "http",
      "Url": "https://api.assetfare.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add odaiin-assetfare -t streamable-http -u 'https://api.assetfare.dev/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 74, +1)

- [security] 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
- [functional regression] 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”

### 2026-09-18 (score 73, +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.

### 2026-09-17 (score 72, +1)

- [security] 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
- [functional regression] 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”

### 2026-09-16 (score 71, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-15 (score 71, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.0 → 0.2.0
- [cosmetic] “assetfare_quote” added an optional parameter “destination_chain”

### 2026-09-14 (score 71)

First indexed and scored.

## MCP tools (22)

### `assetfare_status` (~41 tokens)

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

### `assetfare_manifest` (~29 tokens)

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

### `assetfare_v2_capabilities` (~65 tokens)

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.

### `assetfare_v2_quote` (~120 tokens)

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.

Input parameters:

- `amount_usd` (number, required)
- `from_chain` (string, required)
- `from_token` (string, required)
- `to_chain` (string, required)
- `to_token` (string, required)

### `assetfare_v2_new_session_capability` (~80 tokens)

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.

### `assetfare_v2_prepare` (~151 tokens)

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.

Input parameters:

- `amount_usd` (number, required)
- `caller_approved` (boolean, required)
- `event_signer_public`
- `from_chain` (string, required)
- `from_token` (string, required)
- `to_chain` (string, required)
- `to_token` (string, required)
- `wallets` (object, required)

### `assetfare_v2_session_create` (~163 tokens)

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.

Input parameters:

- `amount_usd` (number, required)
- `caller_approved` (boolean, required)
- `event_signer_public`
- `from_chain` (string, required)
- `from_token` (string, required)
- `idempotency_key` (string, required)
- `session_token` (string, required)
- `to_chain` (string, required)
- `to_token` (string, required)
- `wallets` (object, required)

### `assetfare_v2_session_get` (~58 tokens)

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.

Input parameters:

- `session_id` (string, required)
- `session_token` (string, required)

### `assetfare_v2_session_observe_source` (~82 tokens)

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.

Input parameters:

- `idempotency_key` (string, required)
- `session_id` (string, required)
- `session_token` (string, required)
- `transaction_hashes` (array, required)

### `assetfare_v2_session_observe_output` (~81 tokens)

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.

Input parameters:

- `idempotency_key` (string, required)
- `session_id` (string, required)
- `session_token` (string, required)
- `transaction_hash` (string)

### `assetfare_v2_session_refresh_action` (~69 tokens)

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.

Input parameters:

- `idempotency_key` (string, required)
- `session_id` (string, required)
- `session_token` (string, required)

### `assetfare_quote` (~66 tokens)

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.

Input parameters:

- `amount_usd` (integer, required)
- `destination_chain` (string)

### `assetfare_start_wallet_auth` (~48 tokens)

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

Input parameters:

- `source_wallet` (string, required)

### `assetfare_finish_wallet_auth` (~69 tokens)

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

Input parameters:

- `challenge_id` (string, required)
- `signature` (string, required)
- `source_wallet` (string, required)
- `terms_version` (string, required)

### `assetfare_create_session` (~78 tokens)

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

Input parameters:

- `access_token` (string, required)
- `destination_wallet` (string, required)
- `idempotency_key` (string, required)
- `quote_id` (string, required)
- `source_wallet` (string, required)

### `assetfare_read_session` (~51 tokens)

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

Input parameters:

- `access_token` (string, required)
- `session_id` (string, required)
- `view` (string)

### `assetfare_prepare_source_action` (~46 tokens)

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

Input parameters:

- `access_token` (string, required)
- `session_id` (string, required)

### `assetfare_verify_source_receipt` (~70 tokens)

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

Input parameters:

- `access_token` (string, required)
- `idempotency_key` (string, required)
- `session_id` (string, required)
- `signature` (string, required)

### `assetfare_prepare_cctp_action` (~75 tokens)

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

Input parameters:

- `access_token` (string, required)
- `event_signer_public` (string, required)
- `idempotency_key` (string, required)
- `session_id` (string, required)

### `assetfare_observe_cctp` (~79 tokens)

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.

Input parameters:

- `access_token` (string, required)
- `burn_signature` (string, required)
- `idempotency_key` (string, required)
- `session_id` (string, required)

### `assetfare_prepare_destination_action` (~62 tokens)

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

Input parameters:

- `access_token` (string, required)
- `idempotency_key` (string, required)
- `session_id` (string, required)

### `assetfare_observe_destination` (~69 tokens)

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

Input parameters:

- `access_token` (string, required)
- `idempotency_key` (string, required)
- `session_id` (string, required)
- `transaction_hash` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/odaiin-assetfare/api#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 71

## 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.

## Links

- Remote endpoint: https://api.assetfare.dev/mcp
- Repository: https://github.com/odaiin/assetfare-mcp
- Changelog RSS feed: https://verifymcp.io/servers/odaiin-assetfare/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/odaiin-assetfare/api.json
- HTML version of this page: https://verifymcp.io/servers/odaiin-assetfare/api