AgentPad
Related Servers
Alternatives to AgentPad
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAgent equity markets, credit markets, and capability staking using USDC on Base L2.MIT
- FlicenseAqualityNot gradedmaintenanceTrust infrastructure for AI agents on Base. DEX Spread Oracle (live Uniswap V3 prices), on-chain escrow, insurance pool, and collective knowledge base. 7 smart contracts. Pay-per-query via x402 micropayments in USDC.6-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and interact with onchain agent infrastructure on Base, including identity, micropayments, and tool capabilities via MCP.4MIT

AgentLux MCP Serverofficial
AlicenseAqualityCmaintenanceInstallable AgentLux MCP server and embeddable toolkit for marketplace, identity, creator, services, and social flows on Base.334 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables an autonomous agent wallet on Base to make payments, approve tokens, swap on Uniswap V3, Aerodrome, 0x and CoW Protocol, lend/borrow via Aave V3 and Morpho Blue, trade perps on Hyperliquid, and enforce risk policies via blacklists, caps, simulation, and audit logs.1Creative Commons Zero v1.0 Universal
- AlicenseNot gradedqualityBmaintenanceSettlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * LiMIT
TDQS
Scored across 24 tools
Most build_*_tx tools target distinct actions (launch, buy, sell, vote, claim, finalize, release, burn), but there are real duplicates: agentpad_buy and onboard_and_buy are explicitly 'the same' with a narrow difference, and token_transparency re-includes honest_volume's metrics (per-wallet flows, fee reconciliation, mismatch flags), so an agent could easily pick the wrong one. The quote vs build distinction is clear, and descriptions do mitigate some confusion.
Nearly all transaction tools follow a clean build_<action>_tx pattern, and reads follow get_/list_/quote_/check_ prefixes in snake_case throughout. The deviations are the noun-only standalone names (agentpad_info, agentpad_buy, honest_volume, token_transparency, onboard_and_buy) which break the verb_noun convention but remain readable and predictable in style.
24 tools is on the heavy side for a single protocol surface; the count is partly earned by the launch/team/vote/milestone lifecycle, but redundancy (two near-identical buy flows, analytics duplicated across honest_volume and token_transparency) means several tools do not fully earn their place. It sits in the borderline 16-25 band.
Coverage is strong end-to-end: discovery (info, list_tokens, get_token, get_roadmap), pricing (quote_buy/quote_sell), identity and trading (register, launch, team launch, buy, sell, claim), governance (open votes, eligibility, vote, claim/finalize/release/burn milestones), plus analytics and transparency. I see no obvious missing operation for the stated domain.