Anaxer MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Anaxer Solana data and bounded streaming tools: Do bounded stream tails and returned prices retain observation provenance without adding transaction authority?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read-only real-time Solana DEX token metadata, prices, trades, launches/graduations and bounded live streams.

What we know

Official local stdio wrapper over Anaxer SDK/API. Public docs explicitly describe nine read-only tools and bounded stream tails; no trading or transaction execution is exposed.

Maintenance / activity evidence

@anaxer/mcp 0.2.2 published 2026-09-19T12:35:56.428Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read-only market-data access.
API key.
Sensitive access: Wallet/mint filters and market-research queries

No trading authority; primary risk is using market data for high-stakes decisions.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do bounded stream tails and returned prices retain observation provenance without adding transaction authority?

The bounded review of the publisher's documented Anaxer Solana data and bounded streaming tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

No trading authority; primary risk is using market data for high-stakes decisions.
Read-only market-data access.
API key.
Queries/streams go to Anaxer API/WebSocket.
Sensitive access: Wallet/mint filters and market-research queries
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Requires API key.
Live stream tails consume subscription slots.
No reconnect gap recovery in v1.
No hosted remote MCP in v1.

Original activity observations

@anaxer/mcp 0.2.2 published 2026-09-19T12:35:56.428Z

Technical identity

npm/@anaxer/mcp

Exact implementation source: https://www.npmjs.com/package/@anaxer/mcp ↗
Reviewed resource type: MCP Server
Repository identity: Anaxer-v2/anaxer-mcp
Package identity: npm:@anaxer/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@anaxer/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
anaxer.com/docs/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y @anaxer/mcp
Configure / authenticate
MCP100 setup guide
Set ANAXER_API_KEY in the host process env; restart MCP server after any unauthorized socket state because upstream websocket authentication is terminal.
Previously reviewed client configuration / prerequisites: Publisher README requires Node 20+ and ANAXER_API_KEY for Anaxer real-time Solana API; key must be set in MCP process environment rather than passed to a tool as argument.
Check connection
Suggested check
Confirm tool list and a read-only get_token_metadata call on publicly known mint.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `anaxer`, remove the client entry with `claude mcp remove anaxer`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove anaxer

Official Documentation & Sources

What it does

Official local stdio wrapper over Anaxer SDK/API. Public docs explicitly describe nine read-only tools and bounded stream tails; no trading or transaction execution is exposed.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Read-only real-time Solana DEX token metadata, prices, trades, launches/graduations and bounded live streams.

Representative uses

Read token metadata/prices
List token trades
Read creation/graduation events
Tail bounded real-time channels
Inspect market activity

Limitations

Requires API key.
Live stream tails consume subscription slots.
No reconnect gap recovery in v1.
No hosted remote MCP in v1.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API key.
Permissions: Read-only market-data access.
Data handling: Queries/streams go to Anaxer API/WebSocket.
Cost: plan_based
Risk and cautions: No trading authority; primary risk is using market data for high-stakes decisions.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Wallet/mint filters and market-research queries
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read token metadata/prices; List token trades; Read creation/graduation events; Tail bounded real-time channels; Inspect market activity.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @anaxer/mcp. Recorded transport: stdio. Recorded environment-variable notes: ANAXER_API_KEY; ANAXER_BASE_URL (optional). No configuration values are supplied here. Prerequisites: Node 20+; Anaxer account/key. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Anaxer API key.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only market-data access.

What data-handling boundary should I consider?

Queries/streams go to Anaxer API/WebSocket. Recorded sensitive-access context: Wallet/mint filters and market-research queries.

What limitations and risks should I check before use?

No trading authority; primary risk is using market data for high-stakes decisions. Requires API key. Live stream tails consume subscription slots. No reconnect gap recovery in v1. No hosted remote MCP in v1. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.