_ registry / mcp streamable-http · checked 2h ago

shingou

https://api.shingou.io

Registry code: b4d28f0f1deab89c

api record

Shingou publishes one news-sentiment signal per crypto asset per hour (score in [-1,1], confidence in [0,1], direction, dominant event types, source articles). Honest uses: filtering entries, sizing by confidence, standing aside on kill-switch events (hack_exploit / regulation / delisting) — never an entry generator, never trade advice. On the free plan, symbols outside BTC-USD/ETH-USD/SOL-USD are served 24h delayed: always compare response timestamps to the current time and disclose staleness instead of presenting delayed data as current.

endpoint
https://api.shingou.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is shingou live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is shingou free to use?
Yes — the hub reached it with no key and no payment.
What tools does shingou have?
4 tools: get_sentiment, get_events, get_sentiment_history, get_symbols.
Is shingou safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 98.7%· all time 98.7%

latency
471ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 379 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get crypto news sentiment signals
  • get sentiment history for backtesting
  • get classified crypto market events
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_symbols reads open 6h ago

    The supported symbol universe with each symbol's free-plan freshness. Static — costs no quota and needs no API key.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_sentiment reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "symbols"
      ],
      "properties": {
        "symbols": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Shingou symbols, e.g. [\"BTC-USD\",\"ETH-USD\"] (see get_symbols)"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_events reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "symbol"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max events (default 20)"
        },
        "symbol": {
          "type": "string",
          "description": "One Shingou symbol, e.g. BTC-USD"
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_sentiment_history reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "symbol",
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Range end, ISO 8601"
        },
        "from": {
          "type": "string",
          "description": "Range start, ISO 8601, e.g. 2026-06-27T00:00:00Z"
        },
        "symbol": {
          "type": "string",
          "description": "One Shingou symbol, e.g. BTC-USD"
        },
        "interval": {
          "enum": [
            "1m",
            "5m",
            "15m",
            "1h",
            "4h",
            "1d"
          ],
          "type": "string",
          "description": "Bucket size (default 1h)"
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b4d28f0f1deab89c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b4d28f0f1deab89c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b4d28f0f1deab89c/badge.svg)](https://brick.blue/agent/b4d28f0f1deab89c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.