# AssetFare [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/assetfare/assetfare-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/assetfare-2

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "assetfare": {
    "command": "npx",
    "args": ["--yes","--package=assetfare-mcp","assetfare-verify"]
  }
}
```

## Documentation

## What AssetFare MCP server does

AssetFare MCP server exposes cross-chain route intelligence for agents and wallets without taking transaction authority. Its canonical route is native USDC from Solana to Base, while the service also describes routes across nineteen chains, twenty-four endpoints, and 100 directed routes. Solana SOL to Base USDC and Optimism USDC to Base USDC are specifically supported.

The current v2 profile covers a signed manifest, capabilities discovery, route selection, selected-candidate quoting, direct AssetFare quotes, one-shot caller-approved preparation, and five session-lifecycle operations. A separate legacy endpoint retains thirteen unversioned tools for the original Solana SOL to Base or Arbitrum ETH workflow. The v2 and legacy profiles are not combined on one remote endpoint.

## How it works

Observations are generated for multiple amounts every 30 minutes. A request first uses those observations to shortlist three candidates on six Solana-origin Base and Arbitrum pilot corridors. AssetFare then quotes those candidates at the exact requested amount and returns no more than two options that fit the selected time profile. Balanced uses a 60-second default, fast uses 30 seconds, and economy is explicitly slower. A candidate outside the time limit may remain available as reference information rather than as a selected option.

While a quote remains valid, selection reuses its request-time quote. After expiry, only the selected candidate is refreshed at the same amount; the service does not silently replace it with another route. A later approval can choose one-shot or session execution and may only tighten maximum-input or minimum-output bounds. Multi-step routes require session mode. Expiry, replay, route or provider changes, wallet-chain changes, signer requirement changes, and mode conflicts fail closed.

The caller verifies the route, approves it, signs the resulting unsigned plan, and submits it. AssetFare does not receive private keys, sign transactions, or submit transactions.

## Setup and configuration

The material describes an optional MCP adapter and a primary remote endpoint, but does not provide installation commands or required environment variables. The service also exposes MCP, A2A, and REST/OpenAPI interfaces. Agents that do not use MCP can consult the APIs.json document, v2 capabilities endpoint, v2 OpenAPI document, provider-status endpoint, and read-only Arazzo workflow listed by the project.

For independent verification, the repository includes an `assetfare-verify` command. Live verification uses the published Ed25519 key and checks the signed manifest, safety bundle, and read-only RPC evidence. Offline verification accepts explicit manifest, bundle, and public-key files and makes no network requests.

## Tools and capabilities

AssetFare MCP server returns route and cost information including the AssetFare 1bp fee, provider fee components, known LayerZero native fees, bounded source-gas estimates, expected all-in cost estimates, and costs that remain unpriced. Quotes include an ordered provider path, normalized chain-and-asset endpoints, base-unit bounds, required retained native balance, and flags describing signing, submission, and route aggregation behavior.

Quote integrity is enforced through canonical hashes, fingerprints, exact paths and providers, wallet and signer requirements, allowed modes, and TTL checks. Every quote remains an unranked candidate; no adapter automatically selects it. The `caller_approved` flag is not proof of human approval.

The portable quote encoding preserves JSON types, exact binary64 representations for finite numbers, byte-sorted object keys, UTF-8 lengths, and the distinction between negative zero and zero. Unsafe integral numbers are rejected unless substituted, reducing cross-language precision ambiguity.

## Limitations and notes

The service is non-custodial and cannot complete a transfer on the caller's behalf. A wallet empty on every supported source chain is outside the stated use case. Best-from amounts are not guarantees, so callers should obtain and confirm a fresh quote. The API accepts USD 1 as a shared technical minimum.

The `price_recommended_for_amount` value is advisory. If it is false, callers should compare a fresh all-in quote when price matters. Service fees are 1 basis point, with Circle, provider, and network fees additional. The repository states that the project uses one public release namespace during the pilot and does not claim incorporation or an independent third-party audit.

_Full upstream README: https://allmcps.com/mcp/assetfare-2/readme_