Crypto Signals MCP logo

Crypto Signals MCP

MCP tools for ForgeMesh crypto market intelligence, forecasts, risk context, whale alerts, and decision audits.

Install Crypto Signals MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "crypto-signals-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "@forgemeshlabs/crypto-signals-mcp"
      ],
      "env": {
        "WALLET_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @forgemeshlabs/crypto-signals-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

The crypto-signals-mcp MCP server connects agents to ForgeMesh Crypto Signals through paid requests on Base. It exposes tools for market signals, risk context, forecasts, historical signals, whale alerts, decision support, audits, and feedback. Install it with npx and provide a dedicated Base wallet private key funded with USDC. Use it when an agent needs ForgeMesh market intelligence for research or decision support, rather than financial advice or trading instructions.

Use cases

  • Query crypto market signals for research
  • Review risk context before analyzing an asset
  • Compare current signals with historical data
  • Inspect whale alerts and forecasts
  • Audit agent-generated crypto decisions

Key features

  • Crypto market signals
  • Risk context and forecasts
  • Historical signal lookup
  • Whale alerts
  • Decision analysis and audits
  • x402 payments on Base

Tools10

What Crypto Signals MCP lets your agent do. Expand a tool for its parameters.

Self-reported~64 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

11/11 checks healthy over the last 53d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @forgemeshlabs/crypto-signals-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.1kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed10Callable tools this server registers over MCP.

How Crypto Signals MCP works

What crypto-signals-mcp does

The crypto-signals-mcp MCP server wraps the ForgeMesh Crypto Signals service at crypto.forgemesh.io. It gives an MCP-compatible agent access to crypto market intelligence, including signals, risk information, forecasts, historical signal data, whale alerts, and decision-oriented analysis.

The package is separate from coinopai-mcp; its tools are directed at ForgeMesh Crypto Signals. The service describes its outputs as research and decision-support information. They are not financial advice and do not provide instructions for market activity.

How it works

The crypto-signals-mcp MCP server runs as a local command launched with npx. When an agent invokes a tool, the wrapper communicates with ForgeMesh Crypto Signals and pays the service wallet through x402 on Base. Payment is made from the configured wallet, so usage consumes the USDC held there.

Each exposed operation has a listed price. The available prices range from $0.005 for feedback submission to $0.15 for a crypto decision request. Agents and operators should account for these per-call charges when deciding how often to request signals, forecasts, or audits.

Setup and configuration

Install and run the package with:

Terminal
npx -y @forgemeshlabs/crypto-signals-mcp

Set WALLET_PRIVATE_KEY to a dedicated Base wallet private key. The README recommends using a low-balance wallet funded only with the USDC intended for agent spending, rather than a primary wallet.

A compatible MCP client can use this configuration:

config.json
{
  "mcpServers": {
    "crypto-signals-mcp": {
      "command": "npx",
      "args": ["-y", "@forgemeshlabs/crypto-signals-mcp"],
      "env": {
        "WALLET_PRIVATE_KEY": "${WALLET_PRIVATE_KEY}"
      }
    }
  }
}

Tools and capabilities

The crypto-signals-mcp MCP server exposes these paid tools:

  • get_crypto_signals ($0.05) for crypto signal data.
  • get_crypto_risk ($0.02) for risk context.
  • get_crypto_signal_history ($0.05) for historical signals.
  • get_crypto_preflight ($0.05) for preflight analysis.
  • get_crypto_decision ($0.15) for decision-oriented output.
  • audit_crypto_decision ($0.07) for auditing a crypto decision.
  • get_crypto_forecast ($0.05) for forecasts.
  • get_single_crypto_signal ($0.05) for an individual signal.
  • get_crypto_whale_alerts ($0.02) for whale alerts.
  • submit_crypto_feedback ($0.005) for feedback submission.

Limitations and notes

A funded Base wallet is required for paid requests. The configured private key should belong to a wallet dedicated to this use, with only the intended USDC balance. Tool outputs are market intelligence for research and decision support; the README explicitly excludes financial advice and market activity instructions.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Crypto Signals MCP

crypto-signals-mcp is an MCP server that connects AI agents to ForgeMesh Crypto Signals at crypto.forgemesh.io. Its main tools retrieve crypto signals, risk context, forecasts, signal history, whale alerts, decision analysis, decision audits, and feedback through paid x402 requests on Base.

Install it with `npx -y @forgemeshlabs/crypto-signals-mcp`. Add the command and package argument to your MCP client configuration, then provide the `WALLET_PRIVATE_KEY` environment variable.

It requires `WALLET_PRIVATE_KEY`. Set it to a dedicated Base wallet private key, and fund that wallet with the USDC intended for agent spending.

Tool calls have per-operation prices ranging from $0.005 to $0.15. The listed prices include $0.02 for risk or whale alerts, $0.05 for several signal and forecast tools, and $0.15 for `get_crypto_decision`.

No. Its outputs are market intelligence for research and decision support, not financial advice or market activity instructions.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCrypto Signals MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/crypto-signals-mcp-2?style=directory)](https://allmcps.com/mcp/crypto-signals-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/crypto-signals-mcp-2"><img src="https://allmcps.com/api/badge/crypto-signals-mcp-2?style=directory" alt="Crypto Signals MCP on AllMCPs" /></a>