Back to Directory/Developer Tools

io.github.forgemeshlabs/crypto-signals-mcp

Crypto Signals by ForgeMesh: market intelligence, calibrated forecasts, whale flows, risk context.

Developer ToolsJavaScriptv0.1.3

Crypto Signals by ForgeMesh

M8ven Score mcpservers.org

Dedicated MCP wrapper for ForgeMesh Crypto Signals, an x402 crypto market-intelligence service.

This is separate from coinopai-mcp. Every tool targets crypto.forgemesh.io and pays the ForgeMesh Crypto Signals service wallet through x402 on Base.

Install

npx -y @forgemeshlabs/crypto-signals-mcp

Configure WALLET_PRIVATE_KEY with a dedicated low-balance Base wallet funded only with the USDC you intend the agent to spend. Never use a primary wallet.

Example MCP configuration:

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

Tools

  • get_crypto_signals — $0.05
  • get_crypto_risk — $0.02
  • get_crypto_signal_history — $0.05
  • get_crypto_preflight — $0.05
  • get_crypto_decision — $0.15
  • audit_crypto_decision — $0.07
  • get_crypto_forecast — $0.05
  • get_single_crypto_signal — $0.05
  • get_crypto_whale_alerts — $0.02
  • submit_crypto_feedback — $0.005

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

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

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

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-forgemeshlabs-crypto-signals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@forgemeshlabs/crypto-signals-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@forgemeshlabs/crypto-signals-mcpnpm

Compatible MCP Clients

io.github.forgemeshlabs/crypto-signals-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More