# Stelar Signals (npm · stelar-signals-mcp)

Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.

- Trust score: 93/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.stelardigital.com`: 84/100, [markdown](https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/api.md), [page](https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/api)
- npm · `stelar-signals-mcp`: 93/100 (this document), [markdown](https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/stelar-signals-mcp.md), [page](https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/stelar-signals-mcp)

## Channel facts

- Registry: `npm`
- Package: `stelar-signals-mcp`
- Version: `1.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to StelarDigital/stelar-signals-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1243 tokens (~103/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add stelardigital-stelar-signals-mcp -- npx -y stelar-signals-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "stelardigital-stelar-signals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stelar-signals-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stelardigital-stelar-signals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stelar-signals-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add stelardigital-stelar-signals-mcp -- npx -y stelar-signals-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stelardigital-stelar-signals-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stelar-signals-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stelardigital-stelar-signals-mcp --command npx --arg -y --arg stelar-signals-mcp
```

### Hermes

```yaml
mcp_servers:
  stelardigital-stelar-signals-mcp:
    command: "npx"
    args: ["-y", "stelar-signals-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "stelardigital-stelar-signals-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stelar-signals-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add stelardigital-stelar-signals-mcp -t stdio -c npx -a -y stelar-signals-mcp
```

### Other

```json
{
  "mcpServers": {
    "stelardigital-stelar-signals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stelar-signals-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 93, +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.

### 2026-09-17 (score 92, +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.

### 2026-09-14 (score 91, +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.

### 2026-09-12 (score 90, +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.

### 2026-09-10 (score 89, +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.

### 2026-09-08 (score 88, +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.

### 2026-09-06 (score 87, +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.

### 2026-09-04 (score 86, +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.

## MCP tools (12)

### `crypto_regime` (~145 tokens)

Crypto market regime classifier

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

### `crypto_sentiment` (~147 tokens)

Crypto / text sentiment scorer

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.

Input parameters:

- `asset` (string): Asset symbol to score sentiment for (omit if using `text`)
- `text` (string): Free text to score (omit if using `asset`)

### `summarize` (~105 tokens)

URL / text summarizer

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.

Input parameters:

- `text` (string): Raw text to summarize directly
- `url` (string): Page URL to fetch and summarize

### `factcheck` (~88 tokens)

Fact-check a claim

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.

Input parameters:

- `claim` (string, required): The factual statement to verify

### `pricecheck` (~102 tokens)

Crypto price + change snapshot

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

### `token_risk` (~113 tokens)

Crypto volatility / drawdown risk regime

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

### `telemetry` (~74 tokens)

Crypto portfolio telemetry (paid: $0.005/call via x402)

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.

### `regime` (~96 tokens)

Market-regime classification (paid: $0.03/call via x402)

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

### `gridparams` (~109 tokens)

Grid-trading parameter recommendation (paid: $0.05/call via x402)

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA
- `capital` (number): Capital in USD (default 1000)

### `sentiment` (~89 tokens)

Crypto/text sentiment score (paid: $0.005/call via x402)

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.

Input parameters:

- `asset` (string): Asset symbol (omit if using `text`)
- `text` (string): Free text to score (omit if using `asset`)

### `risk` (~90 tokens)

Volatility/drawdown risk regime (paid: $0.02/call via x402)

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

### `price` (~85 tokens)

Crypto price + change snapshot (paid: $0.005/call via x402)

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.

Input parameters:

- `asset` (string, required): Asset symbol, one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/stelar-signals-mcp#diagnostics

## Score history

- 2026-09-20: 93
- 2026-09-19: 93
- 2026-09-18: 92
- 2026-09-17: 92
- 2026-09-16: 91
- 2026-09-15: 91
- 2026-09-14: 91
- 2026-09-13: 90
- 2026-09-12: 90
- 2026-09-11: 89
- 2026-09-10: 89
- 2026-09-09: 88
- 2026-09-08: 88
- 2026-09-07: 87
- 2026-09-06: 87
- 2026-09-05: 86
- 2026-09-04: 86
- 2026-09-03: 85
- 2026-09-02: 85
- 2026-09-01: 81
- 2026-08-31: 81
- 2026-08-30: 81
- 2026-08-29: 81
- 2026-08-28: 81
- 2026-08-27: 81
- 2026-08-26: 81
- 2026-08-25: 80

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/stelar-signals-mcp
- Socket report: https://socket.dev/npm/package/stelar-signals-mcp
- Repository: https://github.com/StelarDigital/stelar-signals-mcp
- Website: https://api.stelardigital.com/
- Changelog RSS feed: https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/stelar-signals-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/stelar-signals-mcp.json
- HTML version of this page: https://verifymcp.io/servers/stelardigital-stelar-signals-mcp/stelar-signals-mcp