Degenscan Intel
REMOTE · DEGENSCAN-INTEL.ONRENDER.COM · SCANNED SEP 27
Cross-asset market event intelligence for AI trading agents. Pay per call (USDC/x402) or API key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
remote · degenscan-intel.onrender.com
claude mcp add --transport http tradewr333-lgtm-degenscan-intel 'https://degenscan-intel.onrender.com/mcp'
{
"mcpServers": {
"tradewr333-lgtm-degenscan-intel": {
"url": "https://degenscan-intel.onrender.com/mcp"
}
}
} {
"servers": {
"tradewr333-lgtm-degenscan-intel": {
"type": "http",
"url": "https://degenscan-intel.onrender.com/mcp"
}
}
} [mcp_servers.tradewr333-lgtm-degenscan-intel] url = "https://degenscan-intel.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tradewr333-lgtm-degenscan-intel": {
"type": "remote",
"url": "https://degenscan-intel.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add tradewr333-lgtm-degenscan-intel --url 'https://degenscan-intel.onrender.com/mcp' --transport streamable-http
mcp_servers:
tradewr333-lgtm-degenscan-intel:
url: "https://degenscan-intel.onrender.com/mcp" {
"McpServers": {
"tradewr333-lgtm-degenscan-intel": {
"Transport": "http",
"Url": "https://degenscan-intel.onrender.com/mcp"
}
}
} assistant mcp add tradewr333-lgtm-degenscan-intel -t streamable-http -u 'https://degenscan-intel.onrender.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://degenscan-intel.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of degenscan-intel.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://degenscan-intel.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://degenscan-intel.onrender.com/mcp | HTTPS enforced | 301 | https://degenscan-intel.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
events_since Events since ~353
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
explain Explain event ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
exposure_graph Exposure graph ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | 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. |
No output schema declared.
No examples provided.
impact_for Impact for asset ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | 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. |
No output schema declared.
No examples provided.
regime_snapshot Regime snapshot ~88
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sources_status Sources status ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
universe Universe ~74
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.