Anomaly MCP

What forgemeshlabs/anomaly-mcp MCP server does

The forgemeshlabs/anomaly-mcp MCP server connects MCP clients to the ForgeMesh Anomaly Tracker API. It covers several signal domains through 16 tools: blockchain activity, NFT and DeFi flows, aviation events, GitHub repository activity, mempool behavior, and stablecoin pricing. The service is intended for agents that need to identify unusual sequences and receive an interpreted result, including a score and a human-readable story label.

Blockchain tools can scan supported chains, tokens, wallet addresses, whale activity, NFT collections, and DeFi protocols. Aviation tools inspect emergency squawk codes and regional airspace patterns. GitHub tools identify unusual repository growth, forks, commits, issues, merges, and other activity, including recently merged features in selected Anthropic repositories.

How it works

The forgemeshlabs/anomaly-mcp MCP server acts as a thin client rather than performing the analysis locally. An MCP client sends a tool request to the local process, which calls the hosted API at https://anomaly.forgemesh.io. Most scans return anomaly-related fields such as a sequence score, story, novelty, peak time window, and possible failure modes. Some best-effort tools also report source status and coverage notes so a quiet result can be distinguished from incomplete source coverage.

Supported blockchain choices include Ethereum, Base, and Arbitrum for many tools. Mempool monitoring supports Ethereum and Base, while stablecoin monitoring supports Ethereum, Base, and Arbitrum. Scan windows commonly range from one hour to seven days. GitHub tools accept repository names in owner/repo form where a repository is required.

Paid operations use the x402 protocol and charge USDC per call on Base mainnet. The initial response can provide payment challenge metadata; an agent's x402 client must be configured with a wallet private key to settle those payments. health_check is free, while the other tools have per-call prices listed by the project.

Setup and configuration

Install the package globally with npm or run it directly using npx:

npx -y @forgemeshlabs/anomaly-mcp

The server reads ANOMALY_API_BASE for the API URL. If unset, it uses https://anomaly.forgemesh.io. A Claude Desktop configuration can launch the server with npx, pass -y and @forgemeshlabs/anomaly-mcp as arguments, and set that environment variable explicitly.

No API key is required. Payment settlement for paid calls is a separate concern handled by the agent's x402 client and wallet configuration.

Tools and capabilities

Available capabilities include:

• Check API health and uptime, or inspect SequenceMiner model health by chain.
• Scan chain-wide, token, wallet, whale, NFT, and DeFi activity for anomalies.
• Detect mempool gas spikes, MEV indicators, pending whale swaps, and contract deployment bursts.
• Monitor USDC, USDT, and DAI for depeg signals, spreads, and volume spikes.
• Inspect aviation squawk alerts and regional airspace sequence anomalies.
• Find unusual GitHub star velocity, repository growth, forks, commit patterns, issue activity, and merged Claude-related features.

Limitations and notes

Results depend on the hosted API and its monitored data sources. Token, NFT, and aviation alert tools are explicitly best-effort and include source or coverage information when available. Supported chain, region, token, and time-window values are constrained by each tool's input schema. Paid tools incur USDC charges when their x402 challenges are settled; the listed prices range from $0.01 to $0.05 per call.