assetfare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assetfare_statusA | Read legacy v1 compatibility status and original-corridor safety gates. Use only before the unversioned Solana-SOL-to-Base/Arbitrum-ETH workflow; for every six-chain v2 route use assetfare_v2_capabilities instead. Read-only; makes a network request and never authenticates, signs, submits, or advances a session. |
| assetfare_manifestA | Read the Ed25519-signed release manifest and safety-bundle binding before preparing an action. Example: call this once to verify the current release and contract pins; it never creates state, signs, or submits. |
| assetfare_v2_capabilitiesA | Read the current 76-route capability and live-availability matrix before quoting. Example: confirm solana:USDC->base:USDC is prepare-ready and server_signing/server_submission are false. Read-only; creates no wallet login, session, or action. |
| assetfare_v2_quoteA | Get one fresh fee-inclusive quote and caller-operated unsigned-plan handoff. Example: representative from_chain='solana', from_token='USDC', to_chain='base', to_token='USDC', amount_usd=1000. USD 1 is reachability/schema smoke only. Native-USDC economic comparison starts at USD 50 based on dated 2026-09-23 evidence, not a guarantee AssetFare is cheapest. SOL input includes a swap. Always compare fresh candidates at the actual intended amount. Read-only; never authenticates, prepares, signs, or submits. |
| assetfare_v2_new_session_capabilityA | Local stdio only: generate one caller-owned 256-bit session capability without a network call. Remote MCP/A2A servers deliberately do not expose this helper; remote clients generate 32 random bytes locally, encode them as 43-character base64url without padding, and pass the result to assetfare_v2_session_create and every lifecycle call. The token is a sensitive bearer capability, never a private key. |
| assetfare_v2_prepareA | Return the exact validated versioned Core bundle for the first caller-approved unsigned action after a fresh re-quote. Its payload_sha256 covers the Core bundle with only payload_sha256 omitted; the MCP adapter does not append fields to that hash scope. Example: pass caller_approved=true, the exact route, public wallets, and a caller-owned Solana event signer public key when required. Use instead of session mode for one-shot preview; never call both modes, and AssetFare never signs or submits. |
| assetfare_v2_session_createA | Create one caller-approved receipt-driven workflow and return its current unsigned action. Example: pass a locally generated 256-bit base64url session_token, public wallets, and idempotency_key='create-0001'. Use for multi-step execution, never alongside one-shot prepare; AssetFare never signs or submits. |
| assetfare_v2_session_getA | Read an existing v2 workflow and current unsigned action without advancing it. Example: pass the session_id and its caller-owned session_token after a restart. Read-only; never signs or submits. |
| assetfare_v2_session_observe_sourceA | Record source hashes the caller already signed and submitted, then advance the workflow. Example: transaction_hashes=[''] with idempotency_key='source-0001'. Never pass an unsigned hash; AssetFare observes but never signs or submits. |
| assetfare_v2_session_observe_outputA | Record an already-produced bridge or destination output, then advance the workflow. Example: transaction_hash='' with idempotency_key='output-0001'. AssetFare observes but never signs or submits. |
| assetfare_v2_session_refresh_actionA | Refresh an expired action only while it remains unsubmitted. Example: pass the existing session_id, session_token, and idempotency_key='refresh-0001'. Never refresh a submitted step; AssetFare never signs or submits. |
| assetfare_quoteA | Legacy v1 original-corridor quote: get Solana SOL to Base or Arbitrum ETH pricing. Use only with the unversioned legacy wallet-auth/session tools; for every new or six-chain evaluation use assetfare_v2_quote instead. Read-only; makes a network request and never authenticates, creates a session, prepares an action, signs, or submits. |
| assetfare_start_wallet_authA | Create a short-lived, non-transactional Solana signMessage challenge for the legacy v1 workflow. Use only after selecting a fresh legacy assetfare_quote and obtaining caller approval; v2 quote and session tools do not use wallet authentication. Makes a network request and creates login-challenge state, but cannot move funds, sign, or submit. |
| assetfare_finish_wallet_authA | Verify the caller's signature over the exact legacy login challenge and return a sensitive wallet-bound access token. Use only after assetfare_start_wallet_auth; do not use for a v2 session, transaction signature, or arbitrary message. Makes a network request and consumes login-challenge state, but never signs or submits. |
| assetfare_create_sessionA | Lock one fresh legacy assetfare_quote into a wallet-bound v1 execution session. Use only after legacy wallet authentication for the original Solana-SOL-to-Base/Arbitrum-ETH workflow; for a v2 quote use assetfare_v2_session_create instead. Makes a network request and reserves the caller's one active legacy session slot, but creates no blockchain transaction and never signs or submits. |
| assetfare_read_sessionA | Read a legacy v1 session summary, workflow state, receipt, or current unsigned action. Use to inspect or resume a session created by assetfare_create_session; for a v2 session use assetfare_v2_session_get instead and do not use this call to advance state. Read-only and makes a network request; never signs or submits. |
| assetfare_prepare_source_actionA | Prepare the bounded unsigned Solana source action for the current legacy v1 session step. Use only after assetfare_create_session and explicit caller approval; for a v2 route use assetfare_v2_prepare or assetfare_v2_session_create instead. Makes a network request and advances preparation state, but never signs or submits. |
| assetfare_verify_source_receiptA | Verify a finalized Solana source signature already submitted by the caller and advance the legacy v1 workflow. Use only after the caller independently submits assetfare_prepare_source_action; for a v2 session use assetfare_v2_session_observe_source instead. Requires caller approval and makes a network request, but never signs or submits. |
| assetfare_prepare_cctp_actionA | Prepare the unsigned CCTP burn for the current legacy v1 session using a caller-owned event signer public key. Use only when the legacy workflow reports this as the next action; for v2 routes use assetfare_v2_prepare or assetfare_v2_session_create instead. Requires caller approval and advances preparation state, but never receives the event signer private key, signs, or submits. |
| assetfare_observe_cctpA | Verify Circle attestation and the forwarded Base or Arbitrum USDC mint for a caller-submitted legacy v1 burn, then advance the session record. Use only after the CCTP burn is submitted; use assetfare_read_session for inspection without advancement and a v2 session observe tool for v2 routes. Makes a network request but never signs or submits. |
| assetfare_prepare_destination_actionA | Prepare the exact-cap permit and unsigned ERC-4337 destination settlement plan for the current legacy v1 session. Use only when the legacy workflow reports the destination step and after caller approval; v2 sessions expose their current action through assetfare_v2_session_get. Makes a network request and advances preparation state, but never signs or submits. |
| assetfare_observe_destinationA | Verify an already-submitted destination UserOperation receipt and finalize the legacy v1 workflow record. Use only after the caller independently submits assetfare_prepare_destination_action; for v2 output observation use assetfare_v2_session_observe_output instead. Makes a network request and advances session state, but never signs or submits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| assetfare-trust-manifest | Current signed AssetFare trust manifest. |
TDQS
Scored across 22 tools
The v1/v2 tool pairs and multiple prepare/observe/verify tools could be confused by name alone, but every description explicitly scopes its tool to a specific workflow version and step, making the intended use reasonably clear. The routing language is heavy, but it successfully prevents misselection for an agent that reads carefully.
Legacy tools mostly follow verb_noun naming such as create_session and prepare_source_action, while v2 tools mix verb-first names like v2_quote with object-first names like v2_session_create. The assetfare_ prefix keeps things readable, but the two conventions across v1 and v2 are inconsistent.
At 22 tools, the set is heavy and approaches the bloated range. The count is partially justified because the server supports both a legacy v1 workflow and a newer v2 workflow, but the parallel surfaces make the overall surface feel larger than necessary.
Both workflow versions cover the full lifecycle from quoting and session creation through source observation and destination finalization, with refresh and idempotency support. The main gap is the lack of any explicit cancel or abandon operation for a session, though callers can presumably let sessions expire.