_ registry / mcp http-sse · checked 13h ago

degenscan-intel

https://degenscan-intel.onrender.com

Registry code: c10fd2b1bbcdc3d6

api record

Degenscan Intel: cross-asset event feed for trading agents. Events are normalized from ~40 primary sources (SEC, Fed, Federal Register, USGS, NHC, Nasdaq halts, DefiLlama, Polymarket…) and scored against an exposure graph into per-asset impacts.

Typical loop: regime_snapshot → events_since(since='4h', universe=[your book]) → impact_for(asset_id) for anything with confidence ≥ 0.4 → check tradable_now / next_open before acting. For prediction markets: polymarket_context(market) → compare yes_prob with fresh primary-source events.

endpoint
https://degenscan-intel.onrender.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
206ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 8 tools
3 open 5 never probed 3 of 8 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.

  • events_since open 13h ago

    List market-moving events since a point in time (natural disasters, regulator actions, central-bank releases, federal rules, SEC filings, trading halts, on-chain hacks, prediction-market shifts), each scored into per-asset impacts (direction −1/0/+1, confidence 0..1, horizon) with tradable_now / next_open per asset. Use it to answer "what happened in the last N hours that affects my book" or, with a past `since`, to backtest. Filter with universe=["NVDA","BTC"] and min_confidence≥0.4 to act on. $0.005/call; 100 free calls/day.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "description": "Full-text query over title/summary (FTS5 syntax), e.g. \"tariff OR sanction\"."
    },
    "kinds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Event kinds or prefixes: [\"reg.\", \"corp.8k\", \"nat.quake\"]."
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1,
      "description": "Max events returned (1..200)."
    },
    "since": {
      "type": "string",
      "default": "4h",
      "description": "Window start: \"30m\", \"4h\", \"2d\" or ISO-8601. Past values work identically (backtesting)."
    },
    "until": {
      "type": "string",
      "description": "Window end (ISO-8601). Default now."
    },
    "universe": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Asset ids to filter impacts by, e.g. [\"NVDA\",\"BTC\",\"CL\"]. Omit for all."
    },
    "min_severity": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Drop events below this severity (0..1). 0.5 keeps market-moving events only."
    },
    "min_confidence": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Min impact confidence (0..1) for the universe filter. 0.4 is a sensible threshold for acting."
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • regime_snapshot open 13h ago

    One-call situational picture for right now: which venues are open (US equities, futures, FX, crypto) and the next opens, 24h event pressure ranked by asset, the highest-severity events, and prediction-market probabilities (Fed, shutdown, tariffs…). Call it first in a session, or every few hours, to decide whether to look deeper. $0.01/call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • sources_status open 13h ago

    Transparency report on the ~40 data connectors: tier (primary/media), cadence, last successful run, items ingested, last error. Use it to judge freshness before trusting a quiet feed, or to see which sources are best-effort. Free.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • impact_for unknown never probed

    Net directional pressure on ONE asset over a window: bias (−1..+1), number of events, strongest supportive and negative drivers, and the source events with rationale and graph path. Use it before entering or sizing a position in that asset, or to explain a move ("why is MSTR down today?"). $0.003/call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1,
      "description": "Max source events returned with the aggregate."
    },
    "since": {
      "type": "string",
      "default": "24h",
      "description": "Lookback window: \"1h\", \"24h\", \"7d\" or ISO-8601. Default 24h."
    },
    "asset_id": {
      "type": "string",
      "description": "Universe asset id (case-insensitive), e.g. NVDA, BTC, CL, US10Y, SPX. Call `universe` to list ids."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • explain unknown never probed

    Plain-language explanation of ONE event's impacts: why each asset got its direction and confidence, the exposure-graph path used, the source document link and corroborating sources. Use it when an impact from events_since/impact_for is surprising and you need the reasoning before acting, or to log a rationale. Takes the event id from those tools. $0.02/call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "event_id"
  ],
  "properties": {
    "event_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • polymarket_context unknown never probed

    Evidence pack for ONE prediction market: resolves a Polymarket market (id, slug or question text) to its current odds, then returns the primary-source events in our feed (regulators, Fed, filings, disasters, hacks…) that bear on the question, with relevance, source tier, corroboration and per-asset impacts. Use it before trading or quoting a probability on Polymarket/Kalshi-style markets ("Fed cut in October?", "ETF approved by year end?"), or to detect a fresh primary event the market hasn't repriced. Information, not a forecast. $0.01/call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "market"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 15,
      "maximum": 50,
      "minimum": 1,
      "description": "Max related events."
    },
    "since": {
      "type": "string",
      "default": "48h",
      "description": "Lookback window for related events: \"6h\", \"48h\", \"7d\". Default 48h."
    },
    "market": {
      "type": "string",
      "description": "Polymarket market id, slug, or the question text itself (e.g. \"Fed rate cut in October?\"). Slugs/ids are resolved via the public Gamma API; text is searched."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • universe unknown never probed

    List every asset id the service scores (top-100 US equities by volume, indices/ETFs, 15 crypto, commodities, FX, rates) with class, name and exposure tags, plus the universe version stamped on every response. Call it once to map your tickers to asset ids before using the other tools. Free.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • exposure_graph unknown never probed

    Who and what an asset is exposed to: suppliers, customers, countries of revenue/production, input commodities, regulators, indices that hold it, correlated assets and critical facilities (fabs, ports, straits) with coordinates. Use it to find second-order trades (an event on TSM → NVDA, AAPL) or to know which regulators/countries to watch for a holding. $0.002/call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "asset_id"
  ],
  "properties": {
    "depth": {
      "type": "integer",
      "default": 2,
      "maximum": 3,
      "minimum": 1,
      "description": "Hops from the asset: 1 = direct suppliers/customers/regulators, 2 = second order (default), 3 = wide."
    },
    "asset_id": {
      "type": "string",
      "description": "Universe asset id, e.g. NVDA, TSM, MSTR, GC. Call `universe` to list ids."
    }
  },
  "additionalProperties": false
}
    arguments 21 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c10fd2b1bbcdc3d6/badge.svg)](https://brick.blue/agent/c10fd2b1bbcdc3d6)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

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.