F
licenseNot graded
qualityD
maintenance56 pay-per-call MCP endpoints for AI agents. Market signals, macro economics, crypto/DeFi, geopolitical intelligence, SEC filings, GitHub velocity, sanctions screening. USDC on Base Mainnet via x402.
-
hyperd-mcp
Officialby hyperd-ai
Related Servers
Alternatives to hyperd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides onchain intelligence tools for Base, including token risk checks, wallet PnL, and leaderboard data, with paid calls settled per-request in USDC via x402.MIT
- FlicenseAqualityDmaintenancePay-per-call tools for AI agents including trust checks, due diligence, market data, and human-verified approvals, settled in USDC on Base via the x402 protocol.16-
- FlicenseNot gradedqualityDmaintenancePay-per-use AI security and research tools for autonomous agents on Base, enabling honeypot detection, risk assessment, wallet analysis, and yield optimization via the x402 protocol.1-
- AlicenseNot gradedqualityDmaintenanceProvides real-time crypto market data for AI agents, including derivatives, liquidations, options, macro, and market regime detection, with pay-per-call via x402 micropayments on Base.250 npmMIT
usenami-mcpofficial
AlicenseAqualityFmaintenancePerp-first funding rate & RWA spread data for AI agents. 30+ CEX/DEX venues, 6 tools (4 x402-paywalled, 2 free), bring-your-own-wallet via Base mainnet.61MIT
TDQS
A3.9/5.0
Scored across 23 tools
Disambiguation4/5
Most tools map to a unique resource+action, and detailed descriptions clarify boundaries (e.g., wallet.risk vs wallet.anomaly vs wallet.persona). The only slight overlap is token.security vs contract.audit, but they target different objects and use cases.
Naming Consistency4/5
The hyperd.<category>.<operation> pattern is consistently followed across nearly all tools, but 'bundle' breaks the pattern by omitting a category, and 'sentiment.token' reverses the expected resource order (token.sentiment would align with token.info/security). Minor deviations in an otherwise predictable scheme.
Tool Count3/5
At 23 tools, the server is in the 16-25 range, which feels heavy for an MCP surface. However, each tool maps to a distinct paid endpoint and the DeFi analytics domain is broad, so the count is defensible but could overwhelm agents.
Completeness4/5
The toolset covers a wide range of DeFi needs: token/contract security, wallet risk/behavior/PnL, market data, quotes, yield, gas, governance, liquidation monitoring, and watch lifecycle. Minor gaps like no watch-update endpoint or transaction history are workarounds, but core workflows are complete.
Maintenance
ActivityInactive
ResponsivenessUnresponsive