Stelar Signals MCP

Official

by StelarDigital

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation4/5
Most tools are distinct, but crypto_regime and token_risk both describe risk/regime for crypto assets, which could cause confusion despite different focuses (market vs. volatility). Other tools like pricecheck, sentiment, factcheck, and summarize are clearly separated.
Naming Consistency4/5
All names use snake_case and are descriptive, but there is a mix of single-word names (factcheck, pricecheck, summarize) and crypto-prefixed names (crypto_regime, crypto_sentiment, token_risk). No major inconsistencies, but not perfectly uniform.
Tool Count5/5
With 6 tools, the server is well-scoped for a crypto signals service. Each tool serves a clear purpose without being overwhelming or too sparse.
Completeness4/5
The set covers market regime, sentiment, price, risk, fact-checking, and summarization. Minor gaps exist (e.g., no on-chain data or advanced technical indicators), but the core signal needs are addressed. The inclusion of general-purpose tools (factcheck, summarize) is a slight deviation from the crypto focus.
Average 4.2/5 across 6 of 6 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 7 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only mentions 'Low-latency' performance but does not disclose safety, destructive potential, or other behaviors. Burden is on description due to missing annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first describes output, second lists use cases and assets. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, but description explains return values (price, changes, signal) and use cases. Single parameter is fully documented. All necessary context provided.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% description coverage for the single parameter (asset enum). Description lists assets again but adds no new meaning beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it provides current price, 24h and 7d percent change, and a bullish/bearish/neutral signal for major crypto assets. Lists specific supported assets. Distinguishes from siblings like crypto_regime or crypto_sentiment.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly mentions use cases: dashboards, bots, alerts. Lists supported assets but does not provide when-not-to-use or explicitly differentiate from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It mentions the tool is powered by a live production bot and returns a verdict, but does not disclose read-only behavior, rate limits, or potential side effects. Missing explicit assurance of non-destructiveness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary purpose, and contains no fluff. Every sentence contributes value, including usage guidance and output description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple classifier with one parameter and no output schema, the description explains the output format (regime + verdict) and supported assets. It could elaborate on how the suitability verdict is determined, but overall it is sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully documents the single 'asset' parameter with an enum and description (100% coverage). The description adds no additional parameter-specific details beyond what the schema already provides, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: classifying market regime (chop/trend_up/trend_down/high_vol) for major crypto pairs, and returning a grid_suitability verdict. This distinguishes it from siblings like crypto_sentiment (sentiment analysis) and pricecheck (price data).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises use before deploying grid bots, mean-reversion, or trend-follow strategies on a specific set of assets (SOL, XLM, etc.). It does not mention when to avoid or compare to sibling tools like crypto_sentiment, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description bears full burden. It mentions using an LLM and returning a score and label, but does not disclose limitations, latency, error cases, or side effects. Could be more transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences plus a usage instruction. No wasted words, key information front-loaded. Very efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description mentions the return format. It is complete for a simple sentiment tool, covering inputs, outputs, and usage constraints. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, baseline 3. The description adds clarity by explaining parameters and emphasizing mutual exclusivity ('EXACTLY ONE'), which goes beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it provides a sentiment score (-1 to +1) with a label, for either raw text or a crypto asset's recent price action. This distinguishes it from siblings like crypto_regime or factcheck.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says to provide exactly one of `text` or `asset` and lists valid assets. It also mentions use cases (trading signals, news pipelines). However, it lacks explicit when-not-to-use or comparison with siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behavioral aspects: it uses an LLM, returns a verdict with confidence and reasoning, and handles edge cases (opinions, need for real-time data). Without annotations, the description adequately informs the agent of the tool's behavior and limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise—two sentences that efficiently convey purpose, output, and usage boundaries. Every sentence adds unique value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description fully covers the tool's functionality: input (a claim), output (verdict, confidence, reasoning), and special cases (returns 'uncertain' for non-factual or real-time claims). No output schema exists, but the description compensates by detailing the return structure. For a simple tool with one parameter, this is complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'claim' is described as 'The factual statement to verify' in both the schema and description. The description adds minimal extra semantic value beyond the schema, so a baseline score of 3 is appropriate given 100% schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: to return a verdict (true/false/uncertain), confidence score, and reasoning for a factual claim. It distinguishes itself from sibling tools (crypto_regime, crypto_sentiment, etc.) by focusing on general fact-checking rather than cryptocurrency-specific analysis.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists use cases: content moderation, guardrails, misinformation screening. It also notes when the tool returns 'uncertain' for opinions or claims needing live data. However, it does not mention when to avoid using it or suggest alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It explains the output (low/med/high regime), the basis (volatility vs 30-day baseline), and the applicability to major crypto assets. It adds context about the underlying classifier and the tool's non-destructive nature. Some limitations or edge cases could be added, but overall it provides good behavioral insight.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, concisely front-loading purpose, use case, and supported assets. No extraneous information; every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description explains the return value (low/med/high regime), the logic (volatility vs baseline), the supported assets, and a use case. It references the sibling tool for context, making it complete for an agent to decide whether to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%—the single 'asset' parameter is fully described with an enum. The description merely restates the supported assets ('One of SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA'), adding no meaning beyond the schema. Baseline 3 is appropriate since the schema already handles semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a volatility/drawdown risk regime (low/med/high) for a major crypto asset, specifically comparing current volatility to a 30-day baseline. It distinguishes itself from the sibling crypto_regime tool by noting it extends the same classifier but focuses on volatility risk. The verb 'tells' and resource 'risk regime' are specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context by stating the tool is 'useful for position sizing and stop-placement logic' and that it extends the classifier behind crypto_regime. This gives implicit guidance on when to use it vs. the sibling tool. However, it does not explicitly state when not to use it or provide exclusionary criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Discloses that it uses an LLM, fetches URL if provided, and outputs a 3-5 sentence summary. Lacks details on limits (e.g., text length, rate limits) but covers core behavior well.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero wasted words. First sentence defines purpose and output; second gives critical usage instruction. Perfectly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given only two parameters and no output schema, the description is largely complete. It explains what it does, how to use it, and what output to expect. Could mention error cases or size limits, but not essential for this simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema already provides descriptions for both parameters. Description adds value by clarifying mutual exclusivity ('EXACTLY ONE') and that URL is fetched, which tells the agent how parameters interact.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool summarizes a URL or text via LLM, specifying output length (tight 3-5 sentences). Distinguishes from sibling tools which are in different domains (crypto, fact-checking, etc.), so purpose is unique.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs to provide exactly one of 'url' or 'text'. Provides context: 'For agents/pipelines that need a fast, information-dense digest without running their own LLM call or web fetch.' Does not explicitly mention when not to use, but context implies alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![stelar-signals-mcp MCP server](https://glama.ai/mcp/servers/StelarDigital/stelar-signals-mcp/badges/card.svg)](https://glama.ai/mcp/servers/StelarDigital/stelar-signals-mcp)

Score Badge

Copy to your README.md:

[![stelar-signals-mcp MCP server](https://glama.ai/mcp/servers/StelarDigital/stelar-signals-mcp/badges/score.svg)](https://glama.ai/mcp/servers/StelarDigital/stelar-signals-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/StelarDigital/stelar-signals-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server