Skip to main content
Glama
hydracds

Cardexscan MCP Server

by hydracds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Cardexscan MCP Server

No user-submitted related servers found.

    Related Servers

    • DexPaprika MCP Server

      infinity-smithpl
      A
      license
      A
      quality
      D
      maintenance
      Provides real-time access to cryptocurrency and DEX data across multiple blockchains, enabling users to analyze tokens, pools, trading volumes, and perform technical analysis through DexPaprika's API. No API keys required for seamless integration with AI assistants.
      11
      151 npm
      MIT
    • CryptoQuant MCP Server by CryptoQuantOfficial

      CryptoQuant MCP Serverofficial

      CryptoQuantOfficial
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to access real-time on-chain crypto analytics, whale tracking, and market metrics through natural language queries. It provides access to over 245 endpoints for comprehensive data analysis of assets like Bitcoin, Ethereum, and stablecoins.
      7
      6 npm
      7
      MIT

    • @xrpl-utilities/mcp

      XRPL-Utilities
      A
      license
      B
      quality
      C
      maintenance
      Exposes 17 read-only tools from six XRPL-Utilities services so AI agents can access XRPL wallet analysis, signal feeds, macro telemetry, permissioned asset stacks, RWA tracking, and ETF flow data.
      41
      550 npm
      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

    B3.4/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target distinct resources/actions, but the trade-retrieval cluster (get_global_trades, get_token_trades, get_historical_trades, get_wallet_orders) has overlapping scopes that could cause misselection, and get_pending_orders vs get_wallet_orders requires careful reading to distinguish.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern (get_*, create_*, cancel_*, fill_*). swap_aggregate and swap_build_cbor break the pattern with noun-first phrasing, but overall the convention is predictable.

    Tool Count3/5

    24 tools is on the heavy side, spanning tokens, OTC, DCA, swaps, and analytics. Each tool is defensible given the broad domain, but the count sits at the borderline of feeling bloated for a single server.

    Completeness4/5

    Strong lifecycle coverage: OTC (create/fill/get/cancel), DCA (create/cancel/get), swaps (aggregate/build/submit), plus pricing, pools, and trade history. Minor gaps like wallet balance or swap-route execution confirmation exist but core workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources