agentsolis-mcp
Related Servers
Alternatives to agentsolis-mcp
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceEnables AI agents to operate a user's cryptocurrency escrow account — quoting offers, opening and tracking trades and swaps, reading balances and trade states, and preparing marketplace ads. Any action that moves money is only prepared, returning an approval link the account owner must confirm with two-factor authentication.-
Agoreum MCPofficial
AlicenseAqualityCmaintenanceEnables agents to discover services, place orders and pay for them in USDC held in non-custodial escrow on Base, plus post requests, quote, deliver and settle as a provider. Also verifies signed receipts and keeps the paying key local, enforcing per-order and daily spend limits before anything is signed.1834 npm4Apache 2.0- AlicenseAqualityDmaintenanceNon-custodial on-chain escrow + AI arbitration for agent-to-agent USDC payments on Base. Seven tools wrap a verified EscrowV1 contract — create, deliver, confirm, dispute, resolve — with read-only introspection if no wallet key is provided.72MIT

BlurHook MCPofficial
AlicenseAqualityBmaintenanceEnables Robinhood Chain trading agents to obtain quotes, policy-checked unsigned public-swap calldata, simulations, hook information, prices, and deployment discovery without holding keys or signing transactions.9MIT- AlicenseNot gradedqualityNot gradedmaintenanceEnables multi-party conditional escrow locking, autonomous proof-of-delivery release triggers, referral fee splits, and dispute freeze protection for agentic commerce and enterprise settlement workflows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables multi-party conditional escrow locking, autonomous proof-of-delivery release triggers, referral fee splits, and dispute freeze protection for agentic commerce and enterprise settlement workflows.7MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource and action: reading protocol config, computing a fee quote, building unsigned proposal transactions, and reading deal state. The descriptions explicitly delimit scope (read-only vs. calldata-building) and even note where reads overlap, so an agent can pick correctly without guessing.
All names are snake_case verb_noun and readable, but the verb set mixes get_ (twice), quote_, and prepare_, which are semantically apt yet not a single uniform pattern. Minor deviation only; the intent of each name is unambiguous.
Four tools is on the lean side, but for a deliberately read-and-prepare-only server each one earns its place with no redundancy. It is slightly under-scoped rather than bloated.
The surface only covers the buyer's proposal path: config read, fee quote, propose calldata, and status read. The described domain clearly has more lifecycle stages (seller acceptance, funding/deposit, delivery, buyer review/confirm, dispute and arbitration reserve handling) with no tools to support them, so agents will hit dead ends after proposing.