Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Degenscan Intel

REMOTE · DEGENSCAN-INTEL.ONRENDER.COM

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

0 this week 82 Trust /100

Last scanned (15 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 12425 tokens (~161/item across 77 items; 77 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 51% 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 77 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 78 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 0
    • Server version: 0.10.67 → 0.10.68 functional
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “ai_models” rewrote its description, which is the text the model reads security
    • Tool “ai_models_by_task” rewrote its description, which is the text the model reads security
    • Tool “stable_yield_best” rewrote its description, which is the text the model reads security
    • Server version: 0.10.64 → 0.10.67 functional
    • New tool “airfare_benchmark” functional
    • New tool “company_growth_signals” functional
    • New tool “licensed_images” functional
    • New tool “topic_timeline” functional
    • “ai_models” added an optional parameter “q” cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Tool “agent_readiness” rewrote its description, which is the text the model reads security
    • Tool “hl_basis” rewrote its description, which is the text the model reads security
    • Stability: pass → 0.97 functional
    • Server version: 0.10.63 → 0.10.64 functional
    • “agent_readiness” added an optional parameter “peer” cosmetic
    • “calendar” added an optional parameter “min_impact” cosmetic
    • “hl_basis” added an optional parameter “hours” cosmetic
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Server version: 0.10.60 → 0.10.61 functional
Diagnostics

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 21 Nov 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 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 8d72a13c2c41648513b9d014eb5e0339
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. DS published 19718 13 Verified
onrender.com. No DS 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
MCP tools · 77 exposed · ~11,283 tokens

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 →

Tool Tokens
agent_readiness ~175

Audit a public HTTPS API for AI-agent discoverability and payability: score 0-100, grade, checks[] (openapi, descriptions, llms_txt, x402_discovery, prices_visible, a2a_agent_card, mcp_card, robots_allows) and fixes[]. Add peer=<another API> to compare both check by check: comparison {score_gap, behind_on[], ahead_on[], fix_first[]}. $0.005/call. Use to audit whether a public API can be found and paid for by AI agents (OpenAPI, llms.txt, x402, A2A, MCP) and what to fix.

NameTypeReqDescription
peerstring–optional competitor API to compare against, e.g. https://competitor.example
urlstringyeshttps://your-api.example

No output schema declared.

No examples provided.

ai_adoption ~94

Weekly npm + PyPI downloads (last_7d, prior_7d, wow_pct) and GitHub stars for AI SDKs and frameworks; filter by kind (model_sdk, framework, agents, rag, serving, vector_db, models, agent_payments). $0.003/call. Use to see which AI SDKs/frameworks are growing (downloads, stars).

NameTypeReqDescription
kindstring––

No output schema declared.

No examples provided.

ai_cheapest ~104

Cheapest models meeting needs (tools, json, vision, reasoning, audio, pdf) and min_context, ranked by blended USD per 1M tokens (3:1 in:out). $0.001/call. Use to pick the cheapest LLM that supports what you need (tools, vision, json, context).

NameTypeReqDescription
limitinteger––
min_contextinteger––
needsstring––
providerstring––

No output schema declared.

No examples provided.

ai_cost ~114

Cost per call and for N calls of a workload on each listed model: items[] {id, usd_per_call, usd_total, fits_context}, cheapest. $0.002/call. Use to estimate what a workload costs on several LLMs before choosing one.

NameTypeReqDescription
callsinteger––
input_tokensinteger––
modelsstring–comma-separated ids, e.g. openai/gpt-5,anthropic/claude-sonnet
output_tokensinteger––

No output schema declared.

No examples provided.

ai_models ~157

~450 LLMs: items[] {id, provider, context, max_output, input_per_1m, output_per_1m (USD per 1M tokens), modalities_in, tools, structured_outputs, reasoning}. Filters q (name search, e.g. mimo), provider, needs (tools,json,vision,reasoning,audio,pdf), min_context; sort newest|price|context. $0.002/call. Use to list or filter LLMs by price, context and capabilities.

NameTypeReqDescription
limitinteger––
min_contextinteger––
needsstring––
providerstring––
qstring––
sortstring––

No output schema declared.

No examples provided.

ai_models_by_task ~183

Most downloaded (30 d), liked or trending open models for a task from the Hugging Face Hub API: items[] {id, url, downloads_30d, likes, trending_score, license, license_class, commercial_ok, library}; license=permissive|commercial|copyleft|restricted|custom or a license id (mit, apache-2.0). Tasks: image-classification, speech-to-text, ocr, embeddings, reranking, object-detection, text-to-speech, text-to-image, translation, sentiment… $0.002/call. Use to pick an open model for a task (speech-to-text, OCR, image classification, embeddings…) by real downloads and license.

NameTypeReqDescription
licensestring––
limitinteger––
sortstring––
taskstringyes–

No output schema declared.

No examples provided.

ai_regulation ~94

AI law dates, status and sources: eu (AI Act after Omnibus 2026/1744), us_colorado (SB 26-189), brazil (PL 2338/2023); next_milestone. Not legal advice. $0.002/call. Use for AI law dates and status (EU AI Act, Colorado, Brazil); not legal advice.

NameTypeReqDescription
jurisdictionstring––

No output schema declared.

No examples provided.

ai_research ~88

New arXiv papers per AI topic in 7 and 30 days, weekly_pace_vs_30d. Topics: rag, agents, fine_tuning, mcp, evaluation, quantization, multimodal, reasoning, safety, inference. $0.002/call. Use to see which AI research topics are accelerating on arXiv.

NameTypeReqDescription
topicstring––

No output schema declared.

No examples provided.

airfare_benchmark ~198

Average fare actually paid on a US domestic route from the U.S. DOT Consumer Airfare Report (public domain, quarterly): latest {avg_fare_each_way, passengers_per_day, largest_carrier, lowest_fare_carrier}, year_over_year, lower_fare_carrier, seasonality {cheapest_quarter, priciest_quarter}, nearby_airports {options[], cheapest_alternative} (e.g. MIA vs FLL, JFK vs LGA vs EWR), history[]. Benchmark, not a live quote; ~5–6 month lag. $0.002/call. Use before booking or quoting a US domestic flight: what people actually paid on that route, the cheaper nearby airport and carrier, and the cheapest season.

NameTypeReqDescription
fromstringyes3-letter US airport code, e.g. MIA
tostringyes3-letter US airport code, e.g. JFK

No output schema declared.

No examples provided.

base_balance ~88

Base (8453) balance of one address: eth, usdc and optional token {address, symbol, decimals, balance}, block. $0.001/call. Use to read a Base wallet's ETH, USDC or any ERC-20 balance now.

NameTypeReqDescription
addressstringyes0x wallet
tokenstring–optional ERC-20 contract 0x…

No output schema declared.

No examples provided.

br_premium ~86

Crypto-dollar and BTC premium in Brazil: USDT/USDC-BRL on Mercado Bitcoin vs the official BCB PTAX, BTC-BRL vs BTC-USD (Coinbase) at PTAX and at the on-exchange USDT rate. $0.002/call. Use for Brazil's crypto-dollar/BTC premium vs the official PTAX; not for other FX.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

brief ~160

One-call briefing for ONE asset, everything an operator reads before trading it: net pressure and drivers (24h), headlines with sentiment, recent SEC filings (equities), first-order exposure map, related Polymarket market with odds, upcoming scheduled catalysts (7d) and venue status / tradable_now. Replaces 6 separate calls; ideal once per asset per session or pre-open. $0.1/call. Use when you want everything about ONE asset in one call (replaces ~6 calls); for many assets use events_since + impact_for.

NameTypeReqDescription
asset_idstringyesAsset id, e.g. NVDA, BTC, MSTR, GC.
sincestring–Lookback for events (default 24h).

No output schema declared.

No examples provided.

calendar ~212

Upcoming scheduled catalysts for the next N days: US macro prints (CPI, PPI, jobs, PCE, GDP, retail, JOLTS) with ET times, FOMC decisions and minutes, Treasury auctions and earnings dates seen in the feed, each with the assets it usually moves. Use it to avoid holding through a print or to schedule polling. $0.002/call. Use for upcoming scheduled macro/earnings catalysts; for Treasury auction details use treasury_auctions.

NameTypeReqDescription
daysinteger–Look-ahead window in days (default 7).
min_impactstring–Only events with at least this market impact (high = FOMC, CPI, payrolls, PCE).
typesarray–Filter: macro (CPI/PPI/jobs/PCE/GDP/retail/JOLTS), fomc (decisions+minutes), earnings, auctions. Default all.
universearray–For earnings: restrict to these asset ids.

No output schema declared.

No examples provided.

carry_aftermath ~88

Past extreme episodes: onset, hours above threshold, half-life, price return and funding accrued 4/12/24 h later. $0.005/call or Carry key. Use for what happened after past funding extremes (price, funding accrued, half-life).

NameTypeReqDescription
coinstring––
daysinteger––
min_abs_aprnumber––

No output schema declared.

No examples provided.

carry_breakeven ~146

Round-trip cost (2 legs × open/close), break-even days and net return on margin for a funding spread; modes taker / maker1 / maker2; slippage assumed (0.2 % taker, 0.1 % maker) unless given. $0.001/call or Carry key. Use to compute fees/slippage break-even for a funding spread.

NameTypeReqDescription
levnumber––
modestring––
slippage_maker_pctnumber––
slippage_taker_pctnumber––
spread_aprnumberyesDecimal, 0.35 = 35 %/yr

No output schema declared.

No examples provided.

carry_calendar ~73

Funding APR by UTC weekday per dex (or one coin), weekday vs weekend, collapses_on_weekend. $0.003/call or Carry key. Use for weekday/weekend funding patterns per dex or coin.

NameTypeReqDescription
coinstring––
daysinteger––
dexstring––

No output schema declared.

No examples provided.

carry_depth ~79

Hourly order-book depth (USD at 5/10/20/50 bps per side) and spread for one of the 40 most traded perps. $0.002/call or Carry key. Use for order-book depth history of a Hyperliquid perp.

NameTypeReqDescription
coinstringyes–
hoursinteger––

No output schema declared.

No examples provided.

carry_extremes ~91

Funding extremes (|APR| ≥ min_abs_apr, default 2 = 200 %) with realized 24h/7d/14d averages and hours in extreme. $0.003/call or Carry key. Use for funding extremes with realized averages; for history after extremes use carry_aftermath.

NameTypeReqDescription
limitinteger––
min_abs_aprnumber––

No output schema declared.

No examples provided.

carry_funding_matrix ~128

Current annualised funding for every perp on every Hyperliquid dex (main + HIP-3), with OI, 24h volume and spot mark when it exists. Data, not a signal. Requires a Carry Oracle key (US$100/month). Use for ALL perps on ALL Hyperliquid dexes at once; for one coin use price_for or carry_history.

NameTypeReqDescription
dexstring–Filter to one dex: main, xyz, io, para, mkts…
min_volnumber–Minimum 24h volume in USD, default 0

No output schema declared.

No examples provided.

carry_history ~123

Hourly funding/premium/mark/OI/volume for one coin, kept beyond Hyperliquid's 500 h window. HIP-3 coins are prefixed (xyz:NBIS). Requires a Carry Oracle key. Use for one coin's hourly history beyond 500 h; for the current snapshot of all coins use carry_funding_matrix.

NameTypeReqDescription
coinstringyesHyperliquid coin: BTC, ETH… or HIP-3 dex:coin, e.g. xyz:NBIS
hoursnumber–Hours of history, default 720

No output schema declared.

No examples provided.

carry_naked ~119

Perps whose |annualised funding| exceeds a threshold (default 50%) and that have no hedge leg on Hyperliquid (no spot, no same-ticker HIP-3 listing). Raw data, not a call. Requires a Carry Oracle key. Use for funding extremes that cannot be hedged on Hyperliquid; for hedgeable pairs use carry_xdex or carry_spot_perp.

NameTypeReqDescription
min_abs_aprnumber–Threshold on |annualised funding| as a fraction, default 0.5 = 50%

No output schema declared.

No examples provided.

carry_oracle_health ~86

Flags: frozen_funding (0.0 for ≥ 4 h), stale_oracle, divergent_vs_peer (HIP-3 legs, z-score). $0.003/call or Carry key. Use to check frozen funding, stale oracles or diverging HIP-3 legs before trusting a market.

NameTypeReqDescription
dexstring––
hoursinteger––

No output schema declared.

No examples provided.

carry_regime ~110

Per Hyperliquid market (or one coin): % of hours at the 10.95 %/yr floor, in premium, negative or zero over N days, regime now, counts by dex. $0.002/call or Carry key. Use for how often a market sits at the funding floor vs premium; for current levels use carry_funding_matrix.

NameTypeReqDescription
coinstring–Optional coin, HIP-3 prefixed (xyz:NBIS)
daysinteger––

No output schema declared.

No examples provided.

carry_spot_perp ~217

Hyperliquid main-dex perps that also have a Hyperliquid spot market (e.g. HYPE, PURR, BTC via UBTC). Returns items[] with base, perp, funding_apr (annualised, now), funding_apr_14d (14-day mean), hours_positive_14d (share of hours with positive funding, 0–1), perp_mark, spot_mark, spot_pair, basis_pct (perp vs spot, %), perp_vol24_usd, spot_vol24_usd, oi_usd, sorted by 14-day funding. Data, not a signal. Requires a Carry key (X-API-KEY), the free trial key, or x402 per call. Use for main-dex perp vs its spot market; for cross-dex HIP-3 pairs use carry_xdex.

NameTypeReqDescription
limitnumber–Max rows, default 50
min_volnumber–Minimum perp 24h volume in USD, default 100000

No output schema declared.

No examples provided.

carry_watchdog ~71

Every Hyperliquid perp market and dex: status (active/zero_oi/delisted), OI and volume with 7-day change, growth mode, risk flags. Requires a Carry Oracle key. Use for market and dex health (delistings, OI drops); not for funding levels.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

carry_xdex ~227

Assets listed on two or more Hyperliquid HIP-3 dexes (xyz, io, para, mkts…), e.g. NBIS on xyz and io. Returns items[] with base, legs[] (coin, dex, funding_apr now, funding_apr_14d, hours_positive_14d, vol24_usd, oi_usd, mark), spread_apr_now and spread_apr_14d (highest minus lowest leg, annualised), basis_pct (mark difference between legs, %), min_leg_vol24_usd; sorted by 14-day spread. Main-dex tickers are excluded because they can be different assets. Data, not a signal. Requires a Carry key, the free trial key, or x402 per call. Use for the same ticker priced on 2+ HIP-3 dexes; for perp vs spot use carry_spot_perp.

NameTypeReqDescription
limitnumber–Max rows, default 50
min_volnumber–Minimum 24h volume per leg in USD, default 100000

No output schema declared.

No examples provided.

coin_snapshot ~184

Everything about one coin in one call: price {mark, spot, change_24h_pct, basis_pct, realized_vol_30d_ann}, funding {apr_now, apr_8h, apr_24h, open_interest_usd}, liquidations {coverage_pct_of_oi, nearest_long, nearest_short, last_24h}, smart_money {net_usd, long_share_pct, flow_24h_net_usd}, options for BTC/ETH {dvol, atm_iv, rr25, max_pain, put_call_oi}, events_24h {n, bias, top[]}. Blocks are null when unavailable. $0.01/call. Use first when you need the full picture of one coin in one call; then drill down with the specific tools.

NameTypeReqDescription
symbolstringyesBTC, ETH, SOL, HYPE…

No output schema declared.

No examples provided.

company_growth_signals ~192

Growth teardown from primary public sources: attention_jumps[] (months where Wikipedia views or Hacker News mentions jumped, with the events that month and the month before), timeline[] (Show HN / Launch HN, top HN stories, GitHub repos, recent news, first Wayback capture), wikipedia.monthly_views, hacker_news.monthly_story_mentions, github.top_repos. No ads, traffic estimates or backlinks. $0.01/call. Use to reverse-engineer how a company grew from public primary signals: dated attention jumps (Wikipedia, Hacker News) with the launches, repos and news around them.

NameTypeReqDescription
companystringyese.g. Lovable
domainstring–e.g. lovable.dev
githubstring–GitHub org/user if known
monthsinteger––
wikipediastring–exact Wikipedia article title if ambiguous

No output schema declared.

No examples provided.

defi_yields ~113

Stablecoin (or all) DeFi pools above a TVL floor with APY, 30-day mean APY, share paid in reward tokens and DefiLlama outlier flag. Not a risk rating. $0.003/call. Use for stablecoin pool APYs; not a risk rating.

NameTypeReqDescription
chainstring––
include_extremeboolean––
limitinteger––
min_tvlnumber––
stable_onlyboolean––

No output schema declared.

No examples provided.

deribit_perps ~233

Every Deribit perpetual — where Coinbase Advanced / Coinbase for Agents executes international perps (crypto, stocks, gold, oil): items[] {symbol, instrument, margin, mark_price, index_price, premium_bp, funding_8h_pct, funding_apr_pct, open_interest_usd, volume_24h_usd, hyperliquid_funding_apr_pct, funding_gap_vs_hyperliquid_apr_pct}; one symbol adds funding_history {last_24h, last_7d, hourly[]}. sort volume|oi|funding|neg_funding|abs_funding|gap. Not affiliated with Coinbase or Deribit. $0.002/call. Use for Deribit / Coinbase Advanced international perps (Champions Cup venue): funding, OI, premium, gap vs Hyperliquid; for Hyperliquid only use derivs_for or hl_basis.

NameTypeReqDescription
limitinteger––
min_volume_usdnumber––
sortstring––
symbolsstring–comma list, e.g. BTC,SOL,NVDA

No output schema declared.

No examples provided.

derivs_for ~250

Perpetual-futures microstructure for ONE coin from Hyperliquid's public API (no key): hourly funding with 8h-equivalent and annualized %, predicted next funding per venue (Hyperliquid, Binance, Bybit…), open interest in coins and USD with OI-to-24h-volume, mark/oracle/mid and premium vs oracle, 24h notional volume and change, and flags (funding_hot_long/short, premium_rich/discount, oi_heavy_vs_volume). Joined with our primary-source event pressure on the same asset when covered. Use it before sizing a perp position, to detect crowded funding, or as the market-structure leg next to events_since. Liquidations are not included. $0.003/call. Use for one perp's funding/OI with event pressure; for price only use price_for, for every perp use carry_funding_matrix.

NameTypeReqDescription
sincestring–Lookback for our event pressure on the same asset (default 24h).
symbolstringyesPerp coin as listed on Hyperliquid, e.g. BTC, ETH, SOL, HYPE, DOGE. Case-insensitive.

No output schema declared.

No examples provided.

events_since ~384

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. Use to pull the event list for a window/universe; for one asset's scored impacts use impact_for, for a one-call asset summary use brief.

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

No output schema declared.

No examples provided.

explain ~105

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. Use only with an event_id returned by events_since or impact_for.

NameTypeReqDescription
event_idstringyes–

No output schema declared.

No examples provided.

exposure_graph ~179

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. Use to see which assets are linked to one asset; not for prices or events.

NameTypeReqDescription
asset_idstringyesUniverse asset id, e.g. NVDA, TSM, MSTR, GC. Call `universe` to list ids.
depthinteger–Hops from the asset: 1 = direct suppliers/customers/regulators, 2 = second order (default), 3 = wide.

No output schema declared.

No examples provided.

filings_for ~200

SEC EDGAR filings that touch ONE US issuer in the window: 8-K by item (material agreements, results, departures), Form 4 insider trades, 13D/G activist stakes, S-1/424B offerings, bankruptcy — with summary, impact direction and link to the filing. Public-domain source. Use it before earnings or when a stock moves without news. $0.002/call. Use for SEC filings of one issuer; for headlines use news_for.

NameTypeReqDescription
formsarray–Filter: 8k | insider (Form 4) | activist (13D/G) | offering (S-1/424B) | bankruptcy. Default all.
limitinteger––
sincestring–Window: "24h", "7d", "30d". Default 7d.
tickerstringyesUS equity id, e.g. NVDA, TSLA, COIN.

No output schema declared.

No examples provided.

funding_alerts ~169

Which perps have extreme funding RIGHT NOW on Hyperliquid: sorted by |hourly rate| with annualized %, which side is paying (crowded longs vs shorts), open interest and predicted next funding per venue (Hyperliquid, Binance, Bybit). Use every 5–15 min to detect crowded positioning or to pick a side to receive funding. $0.001/call. Use to find which perps have extreme funding now (cross-venue); for every Hyperliquid dex incl. HIP-3 use carry_funding_matrix.

NameTypeReqDescription
limitinteger––
min_abs_rate_1hnumber–Alert threshold on |hourly funding|. Default 0.0003 (=0.03%/h ≈ 263%/yr).

No output schema declared.

No examples provided.

gas_base ~96

Base (8453) gas: base_fee_gwei, next_base_fee_gwei, priority_fee_gwei {p10,p50,p90}, suggested {low,medium,high} EIP-1559 fees, l2_execution_cost {eth_transfer, erc20_transfer, dex_swap} in ETH and USD. $0.001/call. Use before sending a Base transaction to pick fees and estimate cost in USD.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hl_basis ~192

One Hyperliquid main-dex perp: mark_oracle_premium_bps, impact_premium_bps, impact_spread_bps, funding {hourly, per_8h, apr_pct, apr_24h_mean_pct, apr_7d_mean_pct, positive_share_7d_pct}, predicted_funding[] {venue hyperliquid|binance|bybit, apr_pct, next_funding}, open_interest_usd; hours=N (≤168) adds funding_history {stats {mean, min, max, positive_share_pct}, hourly[]}. $0.001/call. Use for one Hyperliquid perp's premium vs oracle and predicted funding vs Binance/Bybit; for the full coin picture use coin_snapshot.

NameTypeReqDescription
coinstringyese.g. BTC, ETH, HYPE
hoursinteger–add hourly funding history for the last N hours

No output schema declared.

No examples provided.

hl_candles ~118

OHLCV candles for one Hyperliquid perp (main or HIP-3): candles[] {t,o,h,l,c,v,trades}, summary {open, close, change_pct, high, low, range_pct, vwap}. $0.001/call. Use for price history (OHLCV) of one Hyperliquid perp; for price now use price_for.

NameTypeReqDescription
coinstringyese.g. BTC or xyz:NBIS
intervalstring––
limitinteger––

No output schema declared.

No examples provided.

hl_liq_near ~98

Hyperliquid coins ranked by tracked notional within within_pct% of liquidation (longs_near_liq_usd, shorts_near_liq_usd) plus confirmed liquidations 24h. $0.001/call. Use to scan which Hyperliquid coins have the most positions close to liquidation.

NameTypeReqDescription
ninteger––
within_pctnumber–Distance from liquidation, %, default 5

No output schema declared.

No examples provided.

hl_liquidations ~170

Liquidation map for one Hyperliquid main-dex coin from the most active accounts (public leaderboard, refreshed every 15 min): longs/shorts {positions, notional_usd, avg_entry}, liquidation_bands[] (side, from_pct/to_pct from mark, price range, notional_usd), nearest_long/short_liquidation {price, distance_pct, cluster_notional_usd}, liquidations_24h (confirmed by Hyperliquid's liquidation marker), coverage_pct_of_oi. A sample, not the whole book. $0.002/call. Use for where Hyperliquid positions get liquidated for one coin; for funding use carry_now.

NameTypeReqDescription
coinstringyesMain-dex coin, e.g. BTC, ETH, HYPE

No output schema declared.

No examples provided.

hl_smart_coin ~182

How the 100 Hyperliquid accounts with the highest 30-day PnL (public leaderboard, ≥ $5M volume, positive ROI) are positioned in one coin: smart {long_positions, short_positions, long_usd, short_usd, net_usd, avg entries}, smart_long_share_pct vs all_tracked_long_share_pct, flow {hours, net_usd, moves, largest[] (account, rank_30d_pnl, action open/add/reduce/close/flip, delta_usd)}. $0.002/call. Use for how top-PnL Hyperliquid traders are positioned in one coin; for all coins use hl_smart_flow.

NameTypeReqDescription
coinstringyesMain-dex coin, e.g. BTC
hoursnumber–Lookback for moves, default 24

No output schema declared.

No examples provided.

hl_smart_flow ~115

Across coins: flows[] {coin, net_usd, bought_usd, sold_usd, moves, accounts} of the top 30-day-PnL Hyperliquid accounts in the last N hours, and positioning[] {coin, net_usd, long_usd, short_usd}. $0.002/call. Use to see where top-PnL Hyperliquid traders are adding or cutting exposure across coins.

NameTypeReqDescription
hoursnumber–Default 4
ninteger––

No output schema declared.

No examples provided.

impact_for ~190

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. Use for one asset's scored impacts; for raw events use events_since, for a full asset briefing use brief.

NameTypeReqDescription
asset_idstringyesUniverse asset id (case-insensitive), e.g. NVDA, BTC, CL, US10Y, SPX. Call `universe` to list ids.
limitinteger–Max source events returned with the aggregate.
sincestring–Lookback window: "1h", "24h", "7d" or ISO-8601. Default 24h.

No output schema declared.

No examples provided.

import_trends ~119

Monthly U.S. imports of an HS code: last_month_value_usd, yoy_month_pct, last_12m_vs_prior_12m_pct, top_origins_last_month[] {country, value_usd, share_pct, unit_value_usd}, monthly[]. $0.003/call. Use for U.S. import value, unit value and origin countries of a product by HS code (Census).

NameTypeReqDescription
hsstringyesHS code, 2/4/6/10 digits, e.g. 9503

No output schema declared.

No examples provided.

keys_trial ~95

Free trial API key for Degenscan Intel: 200 calls, 7 days, no card. Covers the Carry Data tools (carry_*) and the event feed; not the oracle. Then send it as X-API-KEY. One per e-mail. Use once to get a free trial key (200 calls, 7 days); then send it as X-API-KEY.

NameTypeReqDescription
emailstringyes–

No output schema declared.

No examples provided.

licensed_images ~173

Open-licence images for videos and articles (Openverse, Wikimedia Commons, NASA, Met Open Access): items[] {title, image_url, thumbnail_url, page_url, creator, license, commercial_ok, derivatives_ok, attribution_required, credit, source, date}; sources_status{}. We link, never host. Confirm the licence before publishing. $0.002/call. Use to find real images you are allowed to use in a video or article (public domain / Creative Commons) with the credit line; never for AI image generation.

NameTypeReqDescription
commercial_onlyboolean––
limitinteger––
qstringyese.g. apollo 11 launch, wall street 1929, bitcoin mining farm
sourcesstring–openverse,commons,nasa,met

No output schema declared.

No examples provided.

news_for ~173

Headlines that touch ONE asset in the window (press wires, corporate releases, halts, hacks, media), each with source tier, corroboration count, a −1..1 heuristic sentiment score and the asset's impact direction, plus an average sentiment label. Links to the original items; no article bodies. Use it to answer "what is the news flow on X today" or to feed a sentiment gate. $0.002/call. Use for headlines about one ticker; for SEC filings use filings_for.

NameTypeReqDescription
limitinteger––
sincestring–Window: "6h", "24h", "3d". Default 24h.
tickerstringyesAsset id, e.g. NVDA, BTC, MSTR. Call `universe` to list ids.

No output schema declared.

No examples provided.

options_maxpain ~81

Max pain, open interest and put/call ratio for one Deribit expiry (default the next with open interest), BTC or ETH. $0.001/call. Use for one expiry's max pain and open interest only.

NameTypeReqDescription
currencystringyes–
expirystring–DDMMMYY, e.g. 31OCT26

No output schema declared.

No examples provided.

options_summary ~134

BTC or ETH options from Deribit public data: term_structure[] {expiry, days, forward, atm_iv %, rr25 (25d call IV − 25d put IV, vol pts), bf25, open_interest {calls, puts}, max_pain, max_pain_distance_pct}, put_call {oi_ratio, volume_24h_ratio}, dvol {now, change_24h}, top_open_interest[]. $0.002/call. Use for BTC/ETH options implied vol, skew, put/call and max pain; for perp funding use derivs_for.

NameTypeReqDescription
currencystringyes–

No output schema declared.

No examples provided.

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.

remote · degenscan-intel.onrender.com

# add to Claude Code
claude mcp add --transport http tradewr333-lgtm-degenscan-intel 'https://degenscan-intel.onrender.com/mcp'
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 82 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 77 tools: events_since, impact_for, exposure_graph, regime_snapshot, explain, and 72 more. Their descriptions and schemas cost roughly 11,283 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Degenscan Intel MCP server?

VerifyMCP ran 13 checks on Degenscan Intel, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.