F
forgemeshlabs/crypto-signals-mcp
Crypto Signals by ForgeMesh — paid market intelligence MCP via x402 on Base
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"forgemeshlabs-crypto-signals-mcp": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/crypto-signals-mcp"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"forgemeshlabs-crypto-signals-mcp": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/crypto-signals-mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio forgemeshlabs-crypto-signals-mcp -- npx -y @forgemeshlabs/crypto-signals-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · forgemeshlabs/crypto-signals-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 23 sources · mcp
- Install
npx -y @forgemeshlabs/crypto-signals-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y @forgemeshlabs/crypto-signals-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
forgemeshlabs/crypto-signals-mcp;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Crypto Signals by ForgeMesh
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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
bash
npx -y @forgemeshlabs/crypto-signals-mcp
Configure WALLETPRIVATEKEY 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:
json
"mcpServers": {
"crypto-signals-mcp": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/crypto-signals-mcp"],
"env": {
"WALLETPRIVATEKEY": "${WALLETPRIVATEKEY}"
## Requirements
Node.js 20 or newer and a dedicated, low-balance Base wallet (WALLETPRIVATEKEY).
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 X402MAXPRICEUSD and X402SESSIONBUDGETUSD can only lower those caps, never raise them.
## Tools
getcryptosignals — $0.05
getcryptorisk — $0.02
getcryptosignalhistory — $0.05
getcryptopreflight — $0.05
getcryptodecision — $0.15
auditcryptodecision — $0.07
getcryptoforecast — $0.05
getsinglecryptosignal — $0.05
getcryptowhalealerts — $0.02
submitcryptofeedback — $0.005
All outputs are market intelligence for research and decision support, not financial advice or market activity instructions.
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
bash
npx -y @forgemeshlabs/crypto-signals-mcp
Configure WALLETPRIVATEKEY 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:
json
"mcpServers": {
"crypto-signals-mcp": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/crypto-signals-mcp"],
"env": {
"WALLETPRIVATEKEY": "${WALLETPRIVATEKEY}"
## Requirements
Node.js 20 or newer and a dedicated, low-balance Base wallet (WALLETPRIVATEKEY).
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 X402MAXPRICEUSD and X402SESSIONBUDGETUSD can only lower those caps, never raise them.
## Tools
getcryptosignals — $0.05
getcryptorisk — $0.02
getcryptosignalhistory — $0.05
getcryptopreflight — $0.05
getcryptodecision — $0.15
auditcryptodecision — $0.07
getcryptoforecast — $0.05
getsinglecryptosignal — $0.05
getcryptowhalealerts — $0.02
submitcryptofeedback — $0.005
All outputs are market intelligence for research and decision support, not financial advice or market activity instructions.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/forgemeshlabs-crypto-signals-mcp/)
- Source
- awesome · https://github.com/forgemeshlabs/crypto-signals-mcp
- Browse by field
- MCP servers
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.