Skip to main content
Glama
Anaxer-v2

@anaxer/mcp

by Anaxer-v2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ANAXER_WS_URLNoOverride WebSocket URL. Derived from ANAXER_BASE_URL if not set (…/v1/stream).
ANAXER_API_KEYYesYour Anaxer API key (sk_live_...). Required for all API calls.
ANAXER_BASE_URLNoREST base URL. Default: https://api.anaxer.com. Can be set to http://localhost:3010 for a local gateway.https://api.anaxer.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_token_metadataA

Name, symbol, supply, and socials for one mint. Use for 'what is this token' / metadata lookups. 404 → mint not in Anaxer yet (never observed or resolve failed).

get_tokens_metadataA

Batch metadata for up to 50 mints. Missing/never-observed mints are omitted from the array (not errored). Prefer over many get_token_metadata calls.

get_token_priceA

Latest USD + SOL price and market cap for one mint. Use for 'what's X worth now'. 404 → the mint has no live price.

get_token_pricesA

Batch latest prices for up to 50 mints. Missing prices are omitted from the array. Prefer over many get_token_price calls.

list_token_tradesA

One page of recent swaps where mint is either swap leg (REST history, not a live tail). Includes token↔token rows when present. Quote assets (SOL, USDC, USDT) are rejected as mint (use get_token_metadata / get_token_price for those). Optional singular source (e.g. "pump_fun") — NOT an array; for live multi-source filtering use tail_stream with sources. solOnly: true keeps only SOL-paired rows. To page, pass cursor = previous next; stop when next is null. Prefer limit ≤ 20 (default) to conserve context.

list_creationsA

One page of recent token creations (launches). Optional singular source (e.g. "pump_fun") — NOT an array; live multi-source use tail_stream with sources. Use excludeMayhem=true to drop mayhem-mode launches. To get more, call again with cursor set to the previous next; stop when next is null.

list_graduationsA

One page of recent graduations/migrations. Optional singular source (NOT an array). Use minLiquiditySol / excludeMayhem to filter junk. To get more, call again with cursor set to the previous next; stop when next is null.

get_launchpad_statsA

Aggregate launchpad stats (creations/graduations counts) over a rolling window. Use for 'which launchpads are hot'. Optional windowHours.

tail_streamA

Collect a bounded batch of live WebSocket events, then return and unsubscribe. Always terminates: ends when maxEvents (default 20, cap 100) or timeoutMs (default 10000, cap 30000) hits first. filters is a per-channel bag using WS shapes — note sources is an ARRAY (unlike REST list tools' singular source). Valid keys: trades: sources, mints, wallets, minVolumeUsd, maxVolumeUsd, solOnly (quote assets SOL/USDC/USDT rejected in mints — use solOnly for SOL pairs); creations: sources, enriched, excludeMayhem; graduations: sources, excludeMayhem, minLiquiditySol; prices: sources, mints. No transfers channel in v1. Use for short live watches / summaries, not history (history → list_* tools).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.

Resources