Stelar Signals
Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http stelar-signals 'https://api.stelardigital.com/mcp'
{
"mcpServers": {
"stelar-signals": {
"type": "http",
"url": "https://api.stelardigital.com/mcp"
}
}
}
stelar-signals-mcpclaude mcp add stelar-signals -e 'RAPIDAPI_KEY=<your rapidapi_key>' -- npx -y stelar-signals-mcp@1.1.3
{
"mcpServers": {
"stelar-signals": {
"command": "npx",
"args": [
"-y",
"stelar-signals-mcp@1.1.3"
],
"env": {
"RAPIDAPI_KEY": "<your rapidapi_key>"
}
}
}
}
Variables d'environnement
RAPIDAPI_KEYsecret Optional. Needed only for the 6 free-tier tools. The 6 x402 tools require no key.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Stelar Signals MCP
An MCP (Model Context Protocol) server that gives any MCP-compatible agent (Claude Code, Claude Desktop, Cursor, Windsurf, Codex …) live crypto market signals and portfolio telemetry.
Six of its tools are pay-per-call over x402 — no signup, no account, and no API key. Your agent pays cents in USDC on Base from its own wallet and gets the data back in the same request.
Install
claude mcp add stelar -- npx -y stelar-signals-mcp
Or in any MCP client config:
{
"mcpServers": {
"stelar": { "command": "npx", "args": ["-y", "stelar-signals-mcp"] }
}
}
The server starts and lists every tool with no environment variables set.
Paid tools — x402, USDC on Base, no key required
| Tool | Price | What you get |
|---|---|---|
price | $0.005 | Current price, 24h and 7d change, bull/bear/neutral signal |
sentiment | $0.005 | Sentiment score (-1 to +1) and label, for text or an asset |
telemetry | $0.005 | Live telemetry of an AI-managed crypto portfolio — allocation, reconciled P&L, signal votes, human-approval trail |
risk | $0.02 | Volatility / drawdown risk regime — ATR% vs its 30-day p80 baseline, labeled low/med/high |
regime | $0.03 | Market regime (chop / uptrend / downtrend / high-volatility) plus a grid-trading suitability verdict |
gridparams | $0.05 | Grid count, spacing %, price band and per-grid allocation from live 24h market structure |
These call https://api.stelardigital.com, which answers HTTP 402 with a payment
challenge. Any x402-capable client settles it and retries automatically. Assets
covered: SOL, BTC, ETH, XRP, DOGE, LTC, ADA, XLM.
These are live production endpoints backed by real market data — not demo stubs.
Free-tier tools — these DO need a RapidAPI key
crypto_regime, crypto_sentiment, pricecheck, token_risk, summarize,
factcheck are served through RapidAPI. Set RAPIDAPI_KEY to use them:
claude mcp add stelar -e RAPIDAPI_KEY=your-key -- npx -y stelar-signals-mcp
Without the key these six return a clear error; the six paid x402 tools above keep working, because they do not use RapidAPI at all.
Discovery
GET https://api.stelardigital.com/catalog endpoints, prices, parameters
GET https://api.stelardigital.com/.well-known/x402 x402 discovery manifest
GET https://api.stelardigital.com/openapi.json OpenAPI 3.1 spec
A hosted streamable-HTTP MCP endpoint is also live at
https://api.stelardigital.com/mcp.
Honest limits
- Signals cover the eight majors listed above, not arbitrary tokens.
- Paid tools need a funded wallet; without one they return HTTP 402 rather than data.
- Every response carries
generated_at; nothing is cached longer than a minute.
About
Built by Stelar Digital. One human. One AI. A whole company.
MIT licensed.
Questions fréquentes
Qu'est-ce que Stelar Signals ?
Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.
Comment installer Stelar Signals ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http stelar-signals 'https://api.stelardigital.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Stelar Signals ?
Oui. Il attend RAPIDAPI_KEY, à renseigner dans sa configuration.
Stelar Signals est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Stelar Signals ?
Il est publié par StelarDigital. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.