Is Crypto Signals free?

Yes, Crypto Signals is free to use.

How do I install Crypto Signals?

Crypto Signals is a local plugin. Install it using npm package: @forgemeshlabs/crypto-signals-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Crypto Signals safe to use?

Yes. Crypto Signals passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Crypto Signals need?

Crypto Signals requires the following credentials or environment variables: WALLET_PRIVATE_KEY. You can find setup instructions on the server detail page.

What AI apps work with Crypto Signals?

Crypto Signals uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Crypto Signals MCP Server

by ForgeMesh

FinanceLow Risk10.0Local

Free

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

About

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

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (53/55 approved).

5 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Dedicated low-balance Base wallet private key for x402 USDC micropayments. Never use a primary wallet.Required

Environment variable: WALLET_PRIVATE_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-forgemeshlabs-crypto-signals-mcp": {
      "env": {
        "WALLET_PRIVATE_KEY": "your-wallet-private-key-here"
      },
      "args": [
        "-y",
        "@forgemeshlabs/crypto-signals-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Crypto Signals by ForgeMesh

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.