INDIVIDUAL MCP TOOL

impact_for

Net directional pressure on ONE asset over a window: bias (−1.

degenscan-intel.onrender.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://degenscan-intel.onrender.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for impact_for and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

degenscan-intel.onrender.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.degenscan-intel]
url = "https://degenscan-intel.onrender.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "degenscan-intel": {
      "type": "http",
      "url": "https://degenscan-intel.onrender.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: degenscan-intel
Remote MCP URL: https://degenscan-intel.onrender.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "degenscan-intel": {
      "url": "https://degenscan-intel.onrender.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "degenscan-intel": {
      "type": "http",
      "url": "https://degenscan-intel.onrender.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "degenscan-intel",
  "transport": "streamable-http",
  "url": "https://degenscan-intel.onrender.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

events_since — 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.
exposure_graph — 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.
regime_snapshot — 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…).
explain — 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.
polymarket_context — 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.
universe — 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.
sources_status — Transparency report on the ~40 data connectors: tier (primary/media), cadence, last successful run, items ingested, last error.