io.github.forgemeshlabs/crypto-signals-mcp
Crypto Signals by ForgeMesh: market intelligence, calibrated forecasts, whale flows, risk context.
What can you do with io.github.forgemeshlabs/crypto-signals-mcp?
get_crypto_signals— $0.05get_crypto_risk— $0.02get_crypto_signal_history— $0.05get_crypto_preflight— $0.05get_crypto_decision— $0.15audit_crypto_decision— $0.07get_crypto_forecast— $0.05get_single_crypto_signal— $0.05
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@forgemeshlabs/crypto-signals-mcpclaude mcp add crypto-signals-mcp -e 'WALLET_PRIVATE_KEY=<your wallet_private_key>' -- npx -y @forgemeshlabs/crypto-signals-mcp@0.1.6
{
"mcpServers": {
"crypto-signals-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/crypto-signals-mcp@0.1.6"
],
"env": {
"WALLET_PRIVATE_KEY": "<your wallet_private_key>"
}
}
}
}
Environment variables
WALLET_PRIVATE_KEYrequired secret Dedicated low-balance Base wallet private key for x402 USDC micropayments. Never use a primary wallet.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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.ioand 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 variablesX402_MAX_PRICE_USDandX402_SESSION_BUDGET_USDcan only lower those caps, never raise them.
Tools
get_crypto_signals— $0.05get_crypto_risk— $0.02get_crypto_signal_history— $0.05get_crypto_preflight— $0.05get_crypto_decision— $0.15audit_crypto_decision— $0.07get_crypto_forecast— $0.05get_single_crypto_signal— $0.05get_crypto_whale_alerts— $0.02submit_crypto_feedback— $0.005
All outputs are market intelligence for research and decision support, not financial advice or market activity instructions.
Frequently asked questions
What is io.github.forgemeshlabs/crypto-signals-mcp?
Crypto Signals by ForgeMesh: market intelligence, calibrated forecasts, whale flows, risk context.
How do I install io.github.forgemeshlabs/crypto-signals-mcp?
It runs on your machine. In Claude Code: claude mcp add crypto-signals-mcp -e 'WALLET_PRIVATE_KEY=<your wallet_private_key>' -- npx -y @forgemeshlabs/crypto-signals-mcp@0.1.6. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.forgemeshlabs/crypto-signals-mcp need an API key?
Yes. It expects WALLET_PRIVATE_KEY, which you set in its configuration.
Is io.github.forgemeshlabs/crypto-signals-mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.forgemeshlabs/crypto-signals-mcp?
It is published by forgemeshlabs. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.