Dedicated MCP wrapper for ForgeMesh Crypto Signals, an x402 crypto market-intelligence service.
Crypto-signals-mcp source profile. From the maintainer documentation: “Dedicated MCP wrapper for ForgeMesh Crypto Signals, an x402 crypto market-intelligence service.”
The documented npm package is @forgemeshlabs/crypto-signals-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares WALLET_PRIVATE_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| 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 |
{
"mcpServers": {
"crypto-signals-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/crypto-signals-mcp"
],
"env": {
"WALLET_PRIVATE_KEY": "YOUR_WALLET_PRIVATE_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| WALLET_PRIVATE_KEY | Declared in the maintainer’s client configuration. | Check documentation |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.