mcpField
C
crypto-signals-mcp

crypto-signals-mcp

Local
github.com/forgemeshlabsFinance0Updated 3w ago
Repository

About crypto-signals-mcp

crypto-signals-mcp is an MCP server for AI agents that provides ForgeMesh crypto market intelligence, including signals, risk context, forecasts, and whale flows. Calls are paid per use in USDC via x402 on Base, with spending caps.

Key features

  1. 01Retrieve market signals and history
  2. 02Check risk and forecasts
  3. 03View whale alerts
  4. 04Assess and audit decisions
  5. 05Submit signal feedback
  6. 06Constrain x402 spending

Use cases

  1. 01Research crypto market signals
  2. 02Review asset risks and forecasts
  3. 03Add market context to decisions
  4. 04Inspect whale flows

MCP support

Exposes crypto signals, risk, forecasts, and decision-audit tools to MCP clients. Calls settle in USDC via x402 on Base, subject to per-call and per-session spending caps.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "forgemeshlabs-crypto-signals": {
      "command": "npx",
      "args": [
        "-y",
        "@forgemeshlabs/crypto-signals-mcp"
      ],
      "env": {
        "WALLET_PRIVATE_KEY": "<WALLET_PRIVATE_KEY>"
      }
    }
  }
}
Run commandnpx -y @forgemeshlabs/crypto-signals-mcp
Environment variables to set
WALLET_PRIVATE_KEYSecretDedicated low-balance Base wallet private key for x402 USDC micropayments. Never use a primary wallet.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@forgemeshlabs/crypto-signals-mcp0.1.6

Tools

10

Saved tool list · updated 3w ago

This tool takes no parameters.

Details

From the project README

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}"
      }
    }
  }
}

Requirements

  • Node.js 20 or newer and a dedicated, low-balance Base wallet (WALLET_PRIVATE_KEY).
  • Spending caps: the server only talks to https://crypto.forgemesh.io and refuses to sign for any other payee, any network except Base mainnet, any asset except USDC, or any amount above the built-in $0.15 per-call and $10 per-session caps. The environment variables X402_MAX_PRICE_USD and X402_SESSION_BUDGET_USD can only lower those caps, never raise them.

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.