Shingou
REMOTE · API.SHINGOU.IO · 2 COMPONENTS · SCANNED AUG 3
Hourly crypto news sentiment and typed market events, with sources on every signal.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 515 tokens (~128/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.shingou.io
claude mcp add --transport http io-shingou-sentiment https://api.shingou.io/mcp
[mcp_servers.io-shingou-sentiment] url = "https://api.shingou.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-shingou-sentiment": {
"type": "remote",
"url": "https://api.shingou.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-shingou-sentiment --url https://api.shingou.io/mcp --transport streamable-http
mcp_servers:
io-shingou-sentiment:
url: "https://api.shingou.io/mcp" {
"mcpServers": {
"io-shingou-sentiment": {
"type": "http",
"url": "https://api.shingou.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +1
- Schema quality: good → excellent functional
- Server version: 0.3.0 → 0.3.1 functional
- 1 Aug 26 +1
- Server version: 0.2.0 → 0.3.0 functional
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 64
First indexed and scored.
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 3 Aug 2026 · Probed https://api.shingou.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.shingou.io | CN=YR2,O=Let's Encrypt,C=US | 4 Jul 2026 | 2 Oct 2026 | RSA 2048 | SHA256-RSA | 557ff1d15cf4328103059ce0398d7b035b6 |
| SANs: api.shingou.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of api.shingou.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| shingou.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.shingou.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.shingou.io/mcp | HTTPS enforced | 308 | https://api.shingou.io/mcp |
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.
get_events Typed market events ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max events (default 20) |
| symbol | string | yes | One Shingou symbol, e.g. BTC-USD |
No output schema declared.
No examples provided.
get_sentiment Latest sentiment ~103
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 `timestamp` and disclose staleness.
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | array | yes | Shingou symbols, e.g. ["BTC-USD","ETH-USD"] (see get_symbols) |
No output schema declared.
No examples provided.
get_sentiment_history Point-in-time sentiment history ~170
Point-in-time sentiment series for backtesting: `bucket` is the as-of time, no lookahead. `from`/`to` are clamped to your plan's history window and to its per-request span, then echoed back — check them rather than assuming. `reconstructed: true` buckets were rebuilt from archival news, not live-collected; disclose the mix in any backtest.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Range start, ISO 8601, e.g. 2026-06-27T00:00:00Z |
| interval | string | — | Bucket size (default 1h) |
| symbol | string | yes | One Shingou symbol, e.g. BTC-USD |
| to | string | yes | Range end, ISO 8601 |
No output schema declared.
No examples provided.
get_symbols Supported symbols ~31
The supported symbol universe with each symbol's free-plan freshness. Static — costs no quota and needs no API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.