Skip to main content
Glama
Sign In
@anaxer/mcp

@anaxer/mcp

by Anaxer-v2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @anaxer/mcp

No user-submitted related servers found.

    Related Servers

    • pump-mcp

      dodo1653
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to watch live Solana token launches, research coins, devs and wallets, and optionally buy, sell, claim creator fees or launch tokens from chat. All data is read straight from on-chain pump.fun events and bonding curves, while trades are simulated first, capped, and signed locally so the private key never leaves the machine.
      10
      MIT

    • @cookinfun/mcp

      cookinfun
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to query Solana and Pump.fun token intelligence, including coordinated wallets, holder quality, KOL positions, wallet reputation, deployer history, and ratings, with per-call USDC payments over x402 or a Pro key.
      8
      71 npm
      MIT

    • Coin Metrics MCP Server

      7BlockLabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query cryptocurrency network and market data through tools for time-series metrics, OHLCV candles, bid/ask quotes, index levels, and asset or market metadata.
      MIT

    • Pump.fun MCP Server

      dexoryn
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with the Pump.fun platform on Solana for creating, buying, and selling meme tokens. Provides comprehensive token management including balance checking, account management, and secure transaction handling.
      6
      8
      ISC
    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

    A4.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: singular vs batch metadata/price, different event types (trades, creations, graduations), aggregated stats, and live streaming. The descriptions reinforce when to use each, and no two tools overlap in functionality.

    Naming Consistency5/5

    Tool names follow a predictable verb_noun pattern: get_ for metadata/price (with pluralization for batch), list_ for historical enumerations, and tail_ for streaming. The convention is consistent and intuitive, with no mixed styles.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a token data API. It covers core operations (metadata, price, history, stats, streaming) without redundancy or unnecessary bloat, making each tool earn its place.

    Completeness5/5

    The tool surface is comprehensive for the domain: it includes metadata, price, trade history, creations, graduations, launchpad stats, and live streaming. Batch versions avoid repeated calls, and the only notable omission (a transfers channel) is explicitly noted as out of scope for v1.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources