
Stdio MCP bridge for crypto trend/regime tools with automatic x402 payments on Base
Stdio MCP bridge for crypto trend/regime tools with automatic x402 payments on Base
·
A stdio MCP bridge for signal-api. It connects Claude Desktop, Claude Code, Cursor or any stdio MCP client to the remote Streamable HTTP MCP endpoint and pays for tools in one of two ways:
X-API-Key to the REST /v1/* routes.Not Signal Messenger.
signal-apiis a crypto market-signal service. This package has no relationship with Signal Messenger or its messaging app.
https://signal-api.shicoars.workers.dev/mcp using Streamable HTTP.SIGNAL_API_KEY, serves paid tools through /v1/* using prepaid credits
and adds get_credit_balance.SIGNAL_API_KEY, detects x402 PaymentRequired responses and signs
USDC payments on Base automatically.MAX_SPEND_USDC in x402 mode.The bridge is useful for clients that only support stdio MCP and do not have native x402 payment support. Clients with native x402 support can connect directly to the remote URL.
SIGNAL_API_KEY)Set SIGNAL_API_KEY to a credit key (sk_...) bought from signal-api. The
bridge then:
/v1/signal, /v1/market-scan, /v1/trend/{asset},
/v1/regime/{asset} and /v1/indicators/{asset} with the X-API-Key header.EVM_PRIVATE_KEY./free/{asset} route for get_sample.get_credit_balance, which reads GET /credits/balance._meta under
signal-api/credits when the API returns those headers.SIGNAL_API_KEY takes precedence when both variables are set.
EVM_PRIVATE_KEY)Without SIGNAL_API_KEY, the bridge works as before: it connects to the remote
MCP endpoint, receives x402 PaymentRequired results, signs USDC payments on
Base with EVM_PRIVATE_KEY, and retries the call. MAX_SPEND_USDC caps the
amount the bridge may authorize per session.
| Tool | x402 price | Credits | Description |
|---|---|---|---|
list_assets | Free | Free | List supported assets, product ids and prices. Call this first. |
get_catalog | Free | Free | Full product catalog with parameters, prices and descriptions. |
get_sample | Free | Free | 1-day-delayed BTC/ETH trend and regime sample. 60 calls/hour per IP. |
get_credit_balance | n/a | Free | Remaining credits for the configured SIGNAL_API_KEY. Credit mode only. |
get_signal | 0.01 USDC | 1 | Combined BTC + ETH daily trend signal. |
get_market_scan | 0.05 USDC | 10 | All catalog assets plus bullish/bearish, RSI and regime rankings. |
get_trend | 0.005 USDC | 1 | Daily LONG/FLAT trend signal and exposure for one asset. |
get_regime | 0.005 USDC | 1 | Bullish/bearish/lateral regime and volatility for one asset. |
get_indicators | 0.005 USDC | 1 | RSI14, MACD, ATR14, Bollinger %B, returns and 30d/90d ranges. |
Network for x402: Base mainnet (eip155:8453), paid in USDC.
Credits are charged per request: get_market_scan costs 10 credits and the other
paid tools cost 1 credit. Insufficient credits return HTTP 402 with the current
balance; an invalid key returns HTTP 401.
Run the published package with npx:
npx -y @shicodiez/crypto-regime-mcpOr install it globally:
npm install -g @shicodiez/crypto-regime-mcpFrom source:
git clone https://github.com/Shicodiez/crypto-regime-mcp.git
cd crypto-regime-mcp
npm installRun the bridge in credit mode:
SIGNAL_API_KEY=sk_... node src/index.jsOr in x402 mode:
EVM_PRIVATE_KEY=0x... MAX_SPEND_USDC=1 node src/index.jsOn Windows PowerShell:
$env:SIGNAL_API_KEY = "sk_..."
node src/index.js$env:EVM_PRIVATE_KEY = "0x..."
$env:MAX_SPEND_USDC = "1"
node src/index.jsThe process communicates over stdio. Diagnostics are written to stderr.
Buy a pack with x402. The starter pack costs 5 USDC and returns 2,000 credits; the pro pack costs 20 USDC and returns 10,000 credits.
POST https://signal-api.shicoars.workers.dev/credits/buy/starterThe first request without payment returns HTTP 402 with the x402 requirements in
the PAYMENT-REQUIRED header. Sign the USDC payment on Base with any x402-capable
client and retry the same request with the signed payload:
curl -i -X POST https://signal-api.shicoars.workers.dev/credits/buy/starter \
-H "PAYMENT-SIGNATURE: <signed x402 payment payload>"A successful response looks like:
{
"key": "sk_...",
"key_type": "api_key",
"pack": "starter",
"credits": 2000,
"balance": 2000,
"payer": "0x...",
"transaction": "0x...",
"note": "Store this key now. It is not stored and cannot be recovered."
}Store the key immediately: signal-api stores only its SHA-256 hash and cannot
show it again. Then set SIGNAL_API_KEY=sk_... in your MCP client and check the
balance at any time:
curl https://signal-api.shicoars.workers.dev/credits/balance \
-H "X-API-Key: sk_..."The same header also works directly on /signal, /p/{id} and /v1/*.
| Variable | Required | Default | Description |
|---|---|---|---|
SIGNAL_API_KEY | One of these two | - | Prepaid credit key (sk_...). Enables credit mode and get_credit_balance. |
EVM_PRIVATE_KEY | One of these two | - | 32-byte hex private key (0x...) used to sign x402 payments. Ignored when SIGNAL_API_KEY is set. |
MAX_SPEND_USDC | No | 1 | Maximum USDC the bridge may authorize per session in x402 mode. Set 0 to block paid tools. |
SIGNAL_API_MCP_URL | No | https://signal-api.shicoars.workers.dev/mcp | Remote MCP endpoint. |
SIGNAL_API_URL | No | origin of the MCP URL | REST base URL used in credit mode. |
NETWORK | No | eip155:8453 | x402 network. Base mainnet is the default. |
Edit the Claude Desktop configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonCredit mode:
{
"mcpServers": {
"crypto-regime": {
"command": "npx",
"args": ["-y", "@shicodiez/crypto-regime-mcp"],
"env": {
"SIGNAL_API_KEY": "sk_..."
}
}
}
}x402 mode: replace SIGNAL_API_KEY with EVM_PRIVATE_KEY and optionally
MAX_SPEND_USDC.
Restart Claude Desktop after saving the file.
Credit mode:
claude mcp add crypto-regime \
--env SIGNAL_API_KEY=sk_... \
-- npx -y @shicodiez/crypto-regime-mcpx402 mode:
claude mcp add crypto-regime \
--env EVM_PRIVATE_KEY=0x... \
--env MAX_SPEND_USDC=1 \
-- npx -y @shicodiez/crypto-regime-mcpIf your Claude Code version supports remote MCP with x402 payments, you can add the hosted endpoint directly instead:
claude mcp add --transport http crypto-regime \
https://signal-api.shicoars.workers.dev/mcpFor credit mode or automatic x402 payments, use the stdio bridge above.
Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your
project. Credit mode:
{
"mcpServers": {
"crypto-regime": {
"command": "npx",
"args": ["-y", "@shicodiez/crypto-regime-mcp"],
"env": {
"SIGNAL_API_KEY": "sk_..."
}
}
}
}x402 mode: replace SIGNAL_API_KEY with EVM_PRIVATE_KEY and optionally
MAX_SPEND_USDC.
Reload Cursor after saving the file.
The hosted MCP server is:
https://signal-api.shicoars.workers.dev/mcpTransport: Streamable HTTP.
PaymentRequired result.X-API-Key.MAX_SPEND_USDC in x402 mode. The default is 1 USDC per session.
The bridge refuses payments that would exceed the limit.SIGNAL_API_KEY. Treat it like cash: anyone with the key can spend
its credits. Do not commit it to a repository..env files or keys. The included .gitignore excludes
common local secret files.EVM_PRIVATE_KEY to the local signing library; it is
never sent to signal-api. SIGNAL_API_KEY is sent only to signal-api.Run the tests:
npm testBuild (syntax-check the published sources):
npm run buildThe test suite covers the session spending tracker, USDC amount conversion, credit-mode route mapping, credit error handling and configuration precedence.
MIT. See LICENSE.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add crypto-regime -- npx -y @shicodiez/crypto-regime-mcp{
"mcpServers": {
"crypto-regime": {
"env": {
"SIGNAL_API_KEY": ""
},
"args": [
"-y",
"@shicodiez/crypto-regime-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"crypto-regime","env":{"SIGNAL_API_KEY":""},"args":["-y","@shicodiez/crypto-regime-mcp"],"command":"npx"}'[mcp_servers.crypto-regime]
command = "npx"
args = ["-y", "@shicodiez/crypto-regime-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/crypto-regime-mcp to learn what the "Crypto Regime MCP" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx -y @shicodiez/crypto-regime-mcpclaude mcp add crypto-regime
claude mcp add --transport http crypto-regimenpm install -g @shicodiez/crypto-regime-mcpThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/crypto-regime-mcp)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "crypto-regime-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.