A
licenseC
qualityD
maintenanceEnables AI agents to interact with cryptocurrency ecosystems through wallet management, trading operations (swaps, DCA, limit orders), staking, and multi-chain support starting with Solana.
37
GPL 3.0
assetfare
by assetfare
Related Servers
Alternatives to assetfare
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to obtain on-chain DEX aggregator quotes computed by the on-chain Quoter contract through their own RPC node, returning verified unsigned swap calldata, simulations, token info, deployment registry checks, and live staking solvency. All tools are read-only and keyless, so the agent never signs or holds a private key.748 npm1MIT
- 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
- AlicenseBqualityCmaintenanceEnables AI agents to trade Solana prediction markets, including market creation, betting, claims, and affiliate management, all without exposing private keys.7696 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.95 npm3MIT- FlicenseAqualityAmaintenanceDeFi 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-
TDQS
A3.9/5.0
Scored across 22 tools
Disambiguation3/5
The set contains two complete parallel workflows (legacy v1 and v2) that perform essentially the same operations, so tools like assetfare_quote vs assetfare_v2_quote, assetfare_create_session vs assetfare_v2_session_create, and assetfare_read_session vs assetfare_v2_session_get overlap heavily. The descriptions do explicitly cross-reference each other ('for a v2 session use X instead'), which rescues the boundaries, but misselection risk remains real.
Naming Consistency4/5
Most tools follow a readable verb_noun pattern (create_session, prepare_source_action, observe_cctp) with a consistent assetfare_v2_ prefix grouping the newer tools. The main wrinkle is that the legacy tools carry no version marker while every modern tool is versioned, which is mildly counterintuitive, but the overall scheme is predictable.
Tool Count3/5
At 22 tools this sits at the heavy end of the scale, and roughly half are legacy v1 duplicates of v2 functionality, so several tools feel non-essential for a new caller. The scope is defensible given the multi-step bridge lifecycle, but the parallel-workflow redundancy inflates the surface.
Completeness4/5
The tools cover a full end-to-end lifecycle: capabilities discovery, quoting, session creation, action preparation, source/output observation, action refresh, wallet auth, and manifest verification for both v1 and v2. Minor gaps exist (no session listing, cancel/abort, or explicit finality/settlement read in v2), but core workflows have no dead ends.
Maintenance
ActivityMaintained
ResponsivenessWithin a week