assetfare
Related Servers
Alternatives to assetfare
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI agents to interact with cryptocurrency ecosystems through wallet management, trading operations (swaps, DCA, limit orders), staking, and multi-chain support starting with Solana.37GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform complex crypto operations like cross-chain routing, contract decoding, portfolio management, and anti-rug security checks, returning unsigned transactions for safe signing by the agent.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to trade Solana prediction markets, including market creation, betting, claims, and affiliate management, all without exposing private keys.7625 npm1MIT

@1ly/mcp-serverofficial
AlicenseNot gradedqualityFmaintenanceEnables AI agents to discover, pay for, and sell APIs using crypto on Solana and Base networks, with support for automated x402 payments.65 npm3MIT- FlicenseAqualityFmaintenanceDeFi execution and agent-to-agent economy tools for AI agents — swaps, yield, transfers, policy enforcement, trust scoring, A2A jobs, and P\&L across Ethereum, Base, Arbitrum, and Polygon.311-
- AlicenseAqualityBmaintenanceEnables AI agents to discover Cardano DeFi venues, fetch cross-chain swap quotes into ADA, read balances and positions, and obtain unsigned transactions for the agent to sign with its own keys.91Apache 2.0
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.