Skip to content

Shingou

io.shingou/sentimentshingou.iostreamable-httpv0.3.2Scanned

Hourly crypto news sentiment and typed market events, with sources on every signal.

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • get_eventsRecent classified market events for a symbol.Reads text others writeNo findings

    Why it is in this group

    • The name "get_events" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_sentimentLatest news-sentiment signal per symbol (batch up to 50 in one call — one signal per asset per hour, so never poll faster than hourly).Reads text others writeNo findings

    Why it is in this group

    • The name "get_sentiment" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_sentiment_historyPoint-in-time sentiment series for backtesting: `bucket` is the as-of time, no lookahead.Reads text others writeNo findings

    Why it is in this group

    • The name "get_sentiment_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_symbolsThe supported symbol universe with each symbol's free-plan freshness.No findings

    Why it is in this group

    • The name "get_symbols" says "get": a word for reading.
    Description, as the server wrote it
    The supported symbol universe with each symbol's free-plan freshness. Static — costs no quota and needs no API key.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Oct 22, 2026, 15:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.3.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http sentiment https://api.shingou.io/mcp --header 'x-api-key: <your-x-api-key>'
claude mcp add --transport http sentiment https://api.shingou.io/mcp --header 'x-api-key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sentiment__get_sentiment",
      "mcp__sentiment__get_sentiment_history",
      "mcp__sentiment__get_events",
      "mcp__sentiment__get_symbols"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sentiment. Review it before you use it.

Capability tags behind 3 rules
  • mcp__sentiment__get_sentiment untrusted-input
  • mcp__sentiment__get_sentiment_history untrusted-input
  • mcp__sentiment__get_events untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.shingou/sentiment/verify?hash=63c747272ac8f9235536aef1acedf7fdb88c4e39c39c52c8c771b79037e05628" | jq -e '.changed == false'

Pinned hash 63c747272ac8, from Oct 21, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.shingou/sentiment/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.shingou/sentiment
[![anlyon.dev](https://anlyon.dev/badge/io.shingou/sentiment.svg)](https://anlyon.dev/servers/io.shingou/sentiment)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.