Stelar Signals
NPM · STELAR-SIGNALS-MCP · 2 COMPONENTS · SCANNED SEP 20
Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to StelarDigital/stelar-signals-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1243 tokens (~103/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Stelar Signals MCP server?
Stelar Signals runs locally as an npm package, launched with npx -y stelar-signals-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · stelar-signals-mcp
claude mcp add stelardigital-stelar-signals-mcp -- npx -y stelar-signals-mcp
{
"mcpServers": {
"stelardigital-stelar-signals-mcp": {
"command": "npx",
"args": [
"-y",
"stelar-signals-mcp"
]
}
}
} {
"servers": {
"stelardigital-stelar-signals-mcp": {
"command": "npx",
"args": [
"-y",
"stelar-signals-mcp"
]
}
}
} codex mcp add stelardigital-stelar-signals-mcp -- npx -y stelar-signals-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stelardigital-stelar-signals-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"stelar-signals-mcp"
],
"enabled": true
}
}
} openclaw mcp add stelardigital-stelar-signals-mcp --command npx --arg -y --arg stelar-signals-mcp
mcp_servers:
stelardigital-stelar-signals-mcp:
command: "npx"
args: ["-y", "stelar-signals-mcp"] {
"McpServers": {
"stelardigital-stelar-signals-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"stelar-signals-mcp"
]
}
}
} assistant mcp add stelardigital-stelar-signals-mcp -t stdio -c npx -a -y stelar-signals-mcp
{
"mcpServers": {
"stelardigital-stelar-signals-mcp": {
"command": "npx",
"args": [
"-y",
"stelar-signals-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/stelar-signals-mcp@1.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | StelarDigital/stelar-signals-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/StelarDigital/stelar-signals-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2582593587 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:479528b5ac8b312632002fff44fb5e81b4dfaa5e5569cf89fe481ba541e98c769bf628cfc215d5f0433d4e39fc4a598a12125fc269793f7937161a3eb |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
crypto_regime Crypto market regime classifier ~145
Market regime (chop / trend_up / trend_down / high_vol) for a major crypto pair, computed from live 24h market structure by a production-grade classifier. Returns a grid_suitability verdict (good/poor/etc) telling an agent whether current conditions favor range-bound (grid) strategies or trend-following ones. Use this before deciding to deploy a grid bot, mean-reversion strategy, or trend-follow strategy on SOL, XLM, BTC, ETH, XRP, DOGE, LTC, or ADA.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
No output schema declared.
No examples provided.
crypto_sentiment Crypto / text sentiment scorer ~147
Sentiment score (-1 to +1) with a bullish/neutral/bearish label, for either raw text or a crypto asset's recent price action, via an LLM. Give it EXACTLY ONE of `text` (free-form text to score) or `asset` (one of SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA). Useful for agents building trading signals, news pipelines, or social-listening tools without running their own LLM sentiment call.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset symbol to score sentiment for (omit if using `text`) |
| text | string | – | Free text to score (omit if using `asset`) |
No output schema declared.
No examples provided.
factcheck Fact-check a claim ~88
Fact-check verdict (true / false / uncertain) with a confidence score (0-1) and a 1-2 sentence reasoning for any factual claim, via an LLM. Useful for content moderation, chatbot/agent guardrails, and misinformation screening. Returns 'uncertain' for opinions or claims requiring live/real-time data.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The factual statement to verify |
No output schema declared.
No examples provided.
gridparams Grid-trading parameter recommendation (paid: $0.05/call via x402) ~109
PAID PER CALL ($0.05 USDC on Base via x402). Recommended grid-trading parameters (range, spacing, order size) for a pair and capital amount, derived from live 24h market structure. Unpaid calls return the exact x402 payment terms.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
| capital | number | – | Capital in USD (default 1000) |
No output schema declared.
No examples provided.
price Crypto price + change snapshot (paid: $0.005/call via x402) ~85
PAID PER CALL ($0.005 USDC on Base via x402). Current price, 24h/7d change, and a simple signal for a major crypto asset. Unpaid calls return the exact x402 payment terms.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
No output schema declared.
No examples provided.
pricecheck Crypto price + change snapshot ~102
Current price, 24h and 7d percent change, and a simple bullish/bearish/neutral signal for a major crypto asset. Low-latency market-data lookup for dashboards, bots, and alerts — one of SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
No output schema declared.
No examples provided.
regime Market-regime classification (paid: $0.03/call via x402) ~96
PAID PER CALL ($0.03 USDC on Base via x402). Market regime (chop / trend_up / trend_down / high_vol) plus a grid-suitability verdict, computed from live 24h market structure. Unpaid calls return the exact x402 payment terms.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
No output schema declared.
No examples provided.
risk Volatility/drawdown risk regime (paid: $0.02/call via x402) ~90
PAID PER CALL ($0.02 USDC on Base via x402). Volatility / drawdown risk regime (low / med / high) vs the 30-day baseline for a major crypto asset. Unpaid calls return the exact x402 payment terms.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
No output schema declared.
No examples provided.
sentiment Crypto/text sentiment score (paid: $0.005/call via x402) ~89
PAID PER CALL ($0.005 USDC on Base via x402). Sentiment score (-1..+1) with label for EXACTLY ONE of `text` or `asset`. Unpaid calls return the exact x402 payment terms.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset symbol (omit if using `text`) |
| text | string | – | Free text to score (omit if using `asset`) |
No output schema declared.
No examples provided.
summarize URL / text summarizer ~105
Tight 3-5 sentence summary of a URL or a raw text block, via an LLM. Give it EXACTLY ONE of `url` (a page to fetch and summarize) or `text` (raw text to summarize directly). For agents/pipelines that need a fast, information-dense digest without running their own LLM call or web fetch.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | – | Raw text to summarize directly |
| url | string | – | Page URL to fetch and summarize |
No output schema declared.
No examples provided.
telemetry Crypto portfolio telemetry (paid: $0.005/call via x402) ~74
PAID PER CALL ($0.005 USDC on Base via x402 — no signup, no API key). Telemetry for an AI-managed long-horizon crypto portfolio: allocation, reconciled profit-and-loss, signal votes, and the human-approval trail for every trade. Unpaid calls return the exact x402 payment terms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
token_risk Crypto volatility / drawdown risk regime ~113
Volatility / drawdown risk regime (low / med / high) for a major crypto asset, extending the same classifier behind crypto_regime. Tells an agent whether current volatility is elevated vs its 30-day baseline — useful for position sizing and stop-placement logic. One of SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA |
No output schema declared.
No examples provided.
What is the Stelar Signals MCP server?
Stelar Signals is an MCP server listed in the public MCP registry as io.github.StelarDigital/stelar-signals-mcp. Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key. This page covers its npm package (stelar-signals-mcp).
Is the Stelar Signals MCP server safe to use?
Stelar Signals scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Stelar Signals MCP server expose?
Stelar Signals exposes 12 tools: crypto_regime, crypto_sentiment, summarize, factcheck, pricecheck, and 7 more. Their descriptions and schemas cost roughly 1,243 tokens of context every time the server is loaded.
Is the Stelar Signals MCP server still maintained?
Stelar Signals is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Stelar Signals MCP server under?
Stelar Signals declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.