Skip to main content
Glama
hyperd-ai

hyperd-mcp

Official
by hyperd-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to hyperd-mcp

No user-submitted related servers found.

    Related Servers

    • Omni Service Node

      Luckkyyy23
      F
      license
      Not graded
      quality
      D
      maintenance
      56 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.
      -

    • ulvane-mcp

      fatihaura
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides onchain intelligence tools for Base, including token risk checks, wallet PnL, and leaderboard data, with paid calls settled per-request in USDC via x402.
      16 npm
      MIT

    • dyoe-agent-tools-mcp

      bjyoe2016
      A
      license
      A
      quality
      C
      maintenance
      Trust layer for AI agents: 22 pay-per-call x402 tools for scam and fraud checks, payment pre-flight, wallet screening, policy approvals, contact extraction and company research. Free preview with no wallet; paid calls settle in USDC on Base.
      22
      MIT

    • Base Pulse

      Timothymycompc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run honeypot and owner-power safety checks on Base tokens and to read wallet ETH and USDC balances, with every answer sourced from real chain data and paid per call in USDC via x402.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources