# Degenscan Intel (remote · degenscan-intel.onrender.com)

Cross-asset market event intelligence for AI trading agents. Pay per call (USDC/x402) or API key.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `degenscan-intel.onrender.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/tradewr333-lgtm-degenscan-intel/degenscan-intel.md), [page](https://verifymcp.io/servers/tradewr333-lgtm-degenscan-intel/degenscan-intel)

## Channel facts

- Endpoint: `https://degenscan-intel.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1309 tokens (~187/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Degenscan Intel MCP server?

Degenscan Intel is a hosted endpoint at https://degenscan-intel.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http tradewr333-lgtm-degenscan-intel 'https://degenscan-intel.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tradewr333-lgtm-degenscan-intel": {
      "url": "https://degenscan-intel.onrender.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.tradewr333-lgtm-degenscan-intel]
url = "https://degenscan-intel.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tradewr333-lgtm-degenscan-intel": {
      "type": "remote",
      "url": "https://degenscan-intel.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tradewr333-lgtm-degenscan-intel --url 'https://degenscan-intel.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tradewr333-lgtm-degenscan-intel:
    url: "https://degenscan-intel.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tradewr333-lgtm-degenscan-intel": {
      "Transport": "http",
      "Url": "https://degenscan-intel.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tradewr333-lgtm-degenscan-intel -t streamable-http -u 'https://degenscan-intel.onrender.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 63)

First indexed and scored.

## MCP tools (7)

### `events_since` (~353 tokens)

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..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.

Input parameters:

- `kinds` (array): Event kinds or prefixes: ["reg.", "corp.8k", "nat.quake"].
- `limit` (integer): Max events returned (1..200).
- `min_confidence` (number): Min impact confidence (0..1) for the universe filter. 0.4 is a sensible threshold for acting.
- `min_severity` (number): Drop events below this severity (0..1). 0.5 keeps market-moving events only.
- `q` (string): Full-text query over title/summary (FTS5 syntax), e.g. "tariff OR sanction".
- `since` (string): Window start: "30m", "4h", "2d" or ISO-8601. Past values work identically (backtesting).
- `universe` (array): Asset ids to filter impacts by, e.g. ["NVDA","BTC","CL"]. Omit for all.
- `until` (string): Window end (ISO-8601). Default now.

### `impact_for` (~167 tokens)

Impact for asset

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.

Input parameters:

- `asset_id` (string, required): Universe asset id (case-insensitive), e.g. NVDA, BTC, CL, US10Y, SPX. Call `universe` to list ids.
- `limit` (integer): Max source events returned with the aggregate.
- `since` (string): Lookback window: "1h", "24h", "7d" or ISO-8601. Default 24h.

### `exposure_graph` (~162 tokens)

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. 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.

Input parameters:

- `asset_id` (string, required): Universe asset id, e.g. NVDA, TSM, MSTR, GC. Call `universe` to list ids.
- `depth` (integer): Hops from the asset: 1 = direct suppliers/customers/regulators, 2 = second order (default), 3 = wide.

### `regime_snapshot` (~88 tokens)

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…). Call it first in a session, or every few hours, to decide whether to look deeper. $0.01/call.

### `explain` (~91 tokens)

Explain event

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.

Input parameters:

- `event_id` (string, required)

### `universe` (~74 tokens)

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. Call it once to map your tickers to asset ids before using the other tools. Free.

### `sources_status` (~58 tokens)

Sources status

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tradewr333-lgtm-degenscan-intel/degenscan-intel#diagnostics

## Score history

- 2026-09-27: 63

## Common questions

### What is the Degenscan Intel MCP server?

Degenscan Intel is an MCP server listed in the public MCP registry as io.github.tradewr333-lgtm/degenscan-intel. Cross-asset market event intelligence for AI trading agents. Pay per call (USDC/x402) or API key. This page covers its hosted endpoint (https://degenscan-intel.onrender.com/mcp).

### Is the Degenscan Intel MCP server safe to use?

Degenscan Intel scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Degenscan Intel MCP server expose?

Degenscan Intel exposes 7 tools: events_since, impact_for, exposure_graph, regime_snapshot, explain, and 2 more. Their descriptions and schemas cost roughly 993 tokens of context every time the server is loaded.

### Does the Degenscan Intel MCP server require authentication?

No. We connected to Degenscan Intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Degenscan Intel MCP server still maintained?

Degenscan Intel is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://degenscan-intel.onrender.com/mcp
- Repository: https://github.com/tradewr333-lgtm/degenscan-intel
- Website: https://degenscan-intel.onrender.com/
- Changelog RSS feed: https://verifymcp.io/servers/tradewr333-lgtm-degenscan-intel/degenscan-intel.xml
- Changelog JSON feed: https://verifymcp.io/servers/tradewr333-lgtm-degenscan-intel/degenscan-intel.json
- HTML version of this page: https://verifymcp.io/servers/tradewr333-lgtm-degenscan-intel/degenscan-intel