shingou
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHINGOU_API_KEY | No | Shingou API key. Optional: initialize, tools/list and get_symbols work without one. Needed for get_sentiment, get_sentiment_history and get_events. Free key: shingou.io/dashboard | |
| SHINGOU_MCP_URL | No | Override the MCP endpoint URL. | https://api.shingou.io/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sentimentA | Latest news-sentiment signal per symbol (batch up to 50 in one call — one signal per asset per hour, so never poll faster than hourly). On the free plan, symbols outside BTC-USD/ETH-USD/SOL-USD are 24h delayed: check |
| get_sentiment_historyA | Point-in-time sentiment series for backtesting: |
| get_eventsA | Recent classified market events for a symbol. Kill-switch trio: hack_exploit, regulation, delisting — the reference integrations stand aside for 24h after one. Report the event headline and source link, not just a risk flag. |
| get_symbolsA | The supported symbol universe with each symbol's free-plan freshness. Static — costs no quota and needs no API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct, non-overlapping purpose: current sentiment, historical sentiment, events, and symbol universe. There is no ambiguity in selecting between them.
All tool names follow a consistent 'get_<resource>' pattern, making the API predictable and easy to navigate.
With 4 tools, the server is well-scoped for a sentiment/events data provider. Each tool earns its place without unnecessary bloat or missing essentials.
The tool set covers the full spectrum of the domain: current sentiment, historical series for backtesting, event classification, and symbol metadata. No obvious gaps exist for the stated purpose.