Skip to main content
Glama
CryptoAPIs-io

CryptoAPIs Contracts MCP

Official
by CryptoAPIs-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to CryptoAPIs Contracts MCP

No user-submitted related servers found.

    Related Servers

    • my-x402-mcp

      acceptancestronk01-sudo
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables fetching cryptocurrency token data from DexScreener through payment-protected API calls using x402 middleware, with $0.002 USDC charged per request on Base Mainnet.
      -

    • 100pro-token-risk

      rndrpp
      A
      license
      A
      quality
      C
      maintenance
      Enables pre-trade risk screening for EVM and Solana tokens, returning a one-line verdict with detailed flags on liquidity, ownership, and other risk factors.
      1
      MIT

    • dexscreener

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides DEX price, liquidity, and volume data across multiple chains, including pair details, token pairs, search, and trending tokens.
      232 npm
      1
      MIT
    • tokensift by abetoots

      tokensiftofficial

      abetoots
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only token due-diligence by querying keyless public APIs for honeypot checks, rug-pull risk reports, DexScreener pair/token data, and Solana prices, returning standardized envelopes with caching and rate-limit handling.
      6
      -
    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 3 tools

    Disambiguation5/5

    The tools are clearly separated by blockchain ecosystem: evm_contract_data, solana_contract_data, and system_info. The first two target different chains, and system_info is explicitly a reference tool with no API call, so an agent can easily select the correct tool.

    Naming Consistency5/5

    All tool names use consistent snake_case and are descriptive. The two chain-specific tools follow the same [chain]_contract_data pattern, while system_info remains readable and consistent with the overall naming style.

    Tool Count4/5

    Three tools is a small but workable set for a focused contract-data server. The two chain-specific tools earn their place, though the server feels slightly under-scoped for a product named 'Contracts MCP'.

    Completeness3/5

    The surface covers token details for EVM and Solana contracts and includes useful reference documentation. However, it lacks other contract-related operations such as ABI retrieval, event logs, or transfer queries, leaving notable gaps for broader contract analysis.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources