Degenscan Intel
REMOTE · DEGENSCAN-INTEL.ONRENDER.COM
Cross-asset market event intelligence for AI trading agents. Pay per call (USDC/x402) or API key.
Available components
Last scanned (16 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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 →
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
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 |
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 →
oracle_board Oracle: daily board of standing forecasts ~155
The oracle's standing questions recomputed daily (BTC/ETH/SOL vs price targets, next FOMC decision, most-traded Polymarket markets, upcoming CPI/NFP): for each, probability, 80% interval, base rate, market odds, edge and commitment hash — no waiting, no LLM call, cached. Pass slug to get one forecast with full drivers/failure modes and its history. Poll in a loop for cheap calibrated priors. $0.002/call. Use for today's standing forecasts without waiting; to ask your own question use oracle_forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Optional board slug, e.g. btc-120k-oct31. Omit for the whole board. |
No output schema declared.
No examples provided.
oracle_forecast Oracle: forecast a binary question (async) ~502
Get a CALIBRATED probability for a yes/no market question — e.g. "Will Bitcoin close above 120,000 USD on 2026-10-31?", "Will the Fed cut at the October FOMC?", "Will ETH touch 5,000 before 2026-10-31?". The oracle first assembles live context from Intel (spot, 30d realized vol, funding, OI, Polymarket odds, calendar, recent primary-source events) and computes a volatility base rate; then runs Monte Carlo simulations of LLM agent societies (distinct personas, social graph, optional news shocks) plus a 5-expert panel anchored on the base rate; a reasoning model aggregates with the rule "0.5 is never a default". ASYNC: this call returns { forecast_id, status: "queued", eta_s } in under a second; poll oracle_get(forecast_id) every ~20 s (free) until status = "done" (1–3 min). Result: probability, ci80, disagreement, base_rate, market_odds, edge (probability − market), drivers, failure_modes, confidence, runs[] with belief trajectories, panel[], commitment_hash (sha256 committed before resolution), context_used. Public Brier record: oracle_track_record. $0.25/call (covers ~70 LLM calls). Optional interventions=[{round, news, audience}] inject a shock into the simulated society. Use to ask a NEW binary question (async, returns forecast_id); then poll oracle_get. For today's standing forecasts use oracle_board.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Extra facts, news, market data the caller already has. |
| interventions | array | – | – |
| method | string | – | Force a method; default = router decides. |
| population | integer | – | Agents in each simulated society. |
| question | string | yes | Binary question, e.g. 'Will BTC close above 120k on 2026-10-31?' |
| require_verified | boolean | – | Refuse (HTTP 422, no charge) instead of publishing when a premise the answer depends on cannot be verified live. Human-facing surfaces set this true. |
| resolves_at | string | – | When the question resolves (ISO 8601). |
| rounds | integer | – | Interaction rounds per run (simulated time steps). |
| runs | integer | – | Monte Carlo runs (independent societies). |
No output schema declared.
No examples provided.
oracle_get Oracle: fetch a forecast by id (free) ~148
Poll or retrieve an oracle forecast. While the job runs: { status: "queued"|"running", retry_after_s }. When done: the full Forecast (probability, ci80, disagreement, base_rate, market_odds, edge, summary, drivers, failure_modes, confidence, runs[], panel[], commitment_hash, context_used). Free — results are yours forever; anyone can verify the commitment_hash. Use after oracle_forecast, or with an id from oracle_board / oracle_track_record. Use only to poll a forecast_id returned by oracle_forecast (free).
| Name | Type | Req | Description |
|---|---|---|---|
| forecast_id | string | yes | The forecast_id returned by oracle_forecast or listed by oracle_board / oracle_track_record. |
No output schema declared.
No examples provided.
oracle_track_record Oracle: public Brier track record (free) ~118
How good the oracle has been: Brier score overall and by domain (0.25 = coin flip, 0.15 = good human forecaster, 0.10 = superforecaster), oracle vs. market Brier and beat_market_rate on questions that had a Polymarket price, mean absolute edge, and the 20 most recent commitments (id, probability, hash, outcome). Free. Use it to decide how much to trust oracle_forecast / oracle_board. Use to audit the oracle's public accuracy (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
polymarket_context Polymarket context ~240
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. Use for one market's odds plus related primary-source events; to discover markets use polymarket_top.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max related events. |
| market | string | yes | 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. |
| since | string | – | Lookback window for related events: "6h", "48h", "7d". Default 48h. |
No output schema declared.
No examples provided.
polymarket_edge Polymarket edge (oracle vs market) ~171
Where a calibrated forecaster disagrees most with Polymarket right now: for each open daily-board question matched to a Polymarket market, the oracle probability, 80% interval, market YES price, edge (p − odds), which side looks cheap, base rate, resolution date and a sha256 commitment hash — sorted by |edge|. Cached from the daily board (no LLM, instant); poll it in a loop. Public Brier track record at /v1/oracle/track-record. $0.002/call. Use to list markets where the oracle and market odds disagree most; for one new question use oracle_forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_abs | number | – | Minimum |p − odds|, e.g. 0.03 |
No output schema declared.
No examples provided.
polymarket_events Polymarket events ~114
Most active Polymarket events with top outcomes: items[] {title, end_date, volume_24h_usd, volume_total_usd, open_interest_usd, liquidity_usd, markets, top_outcomes[] {question, yes_prob}, url}. Filters q, tag. $0.002/call. Use for Polymarket event groups (all outcomes of one question family) with open interest.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
polymarket_leaderboard Polymarket leaderboard ~102
Polymarket top traders: items[] {rank, wallet, name, pnl_usd, volume_usd, pnl_to_volume_pct} for day/week/month/all, by pnl or volume. $0.002/call. Use to see which Polymarket traders made the most PnL or volume; for markets use polymarket_top.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | – |
| limit | integer | – | – |
| period | string | – | – |
No output schema declared.
No examples provided.
polymarket_markets Polymarket markets search ~162
Search the ~500 most active open Polymarket markets: items[] {id, slug, question, yes_prob, best_bid, best_ask, spread, change_24h, volume_24h_usd, liquidity_usd, end_date, url}. Filters q (words), tag, ends_within_days, min_liquidity. $0.002/call. Use to search Polymarket markets by words, tag, closing date or liquidity, with bid/ask and spread; for the top list use polymarket_top.
| Name | Type | Req | Description |
|---|---|---|---|
| ends_within_days | number | – | – |
| limit | integer | – | – |
| min_liquidity | number | – | – |
| q | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
polymarket_top Polymarket top markets ~160
The most active Polymarket markets right now (by 24h volume, liquidity or 24h change; optional tag like crypto/fed/politics): question, YES odds, 24h change, volume, liquidity, end date, and a link to our primary-source evidence pack for each. Use it to find where prediction-market money is moving before calling polymarket_context. $0.002/call. Use to find the most active prediction markets; for one market's evidence use polymarket_context, for oracle disagreement use polymarket_edge.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| sort | string | – | – |
| tag | string | – | Optional Gamma tag slug filter, e.g. 'crypto', 'fed', 'politics'. |
No output schema declared.
No examples provided.
price_for Price probe ~137
Cheapest price check for ONE coin, no key: Hyperliquid perp mark/mid/oracle, Coinbase spot, 24h change, perp-spot basis, current funding, plus links to our event pressure on that asset. ~1 KB, cached 30 s — made for polling loops. $0.001/call. Use for one coin's price/basis/funding now; for funding history use carry_history, for all perps at once use carry_funding_matrix.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Coin, e.g. BTC, ETH, SOL, HYPE (Hyperliquid perp mark + Coinbase spot when available) |
No output schema declared.
No examples provided.
product_brief Product research brief ~80
Interest trend (Wikipedia), CPSC recalls and (with hs) U.S. imports for a product in one call. $0.006/call. Use for a one-call product research brief: interest trend, recalls and U.S. imports.
| Name | Type | Req | Description |
|---|---|---|---|
| hs | string | – | – |
| lang | string | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
product_recalls Product recalls (U.S. CPSC) ~140
CPSC recalls by product keyword: count, units_us_total, sold_on_amazon, by_country_of_manufacture[], by_year[], items[] {recall_number, date, title, units_us, hazard, injuries, remedy[], made_in[], importers[], sold_on_amazon, url}. $0.002/call. Use to check U.S. CPSC recalls for a product category (units, hazards, where made, sold on Amazon) before sourcing or selling it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | product keyword, e.g. air fryer |
| since | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
pulse Pulse (1h) ~102
Cheapest first call: how many events hit the feed in the last hour by class (natural, regulatory, central-bank, corporate, crypto, media…), the 3 most severe with their top impacts, and which venues are open. Use it every hour to decide whether anything needs a deeper look, or as a health/probe call. $0.001/call. Use first as a cheap heartbeat; for the events themselves use events_since, for one asset use brief.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
regime_snapshot Regime snapshot ~108
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. Use for the market-wide state (venues open, pressure by asset); for one asset use brief.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sources_status Sources status ~70
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. Use to check the health of each primary source (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stable_yield_best Best stablecoin yield ~141
best_by_asset[] {asset, best {project, chain, apy_pct, apy_base_pct, reward_share_pct, tvl_usd}, best_base_only}, usdc_by_chain[], usdt_by_chain[]; lending markets add lending {borrow_apy_pct, utilization_pct, total_supplied_usd, total_borrowed_usd} and lending_markets{}. $0.001/call. Use for the single best stablecoin yield per asset or chain; for the full pool list use defi_yields.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | USDC, USDT, DAI… |
| min_tvl | number | – | – |
No output schema declared.
No examples provided.
stablecoin_supply Stablecoin supply ~186
Stablecoin supply from DefiLlama. Returns totals_usd_pegged {circulating, change_1d, change_7d, change_30d} in USD, depegged_over_50bps[] (USD stablecoins trading below $0.995 with ≥ $50M supply: symbol, price, depeg_bps, circulating), and items[] per stablecoin (symbol, peg, mechanism, price, circulating, change_1d/7d/30d, change_7d_pct, change_30d_pct, chains), sorted by supply. Net new supply is a proxy for fresh on-chain dollar liquidity. $0.002/call. Use for total stablecoin supply and net change; for individual large transfers use whale_moves.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many stablecoins in items[], default 25 |
No output schema declared.
No examples provided.
token_risk Token risk check (lite) ~120
Quick token contract risk: verdict, score 0-100, honeypot, buy_tax, sell_tax, mintable, critical[]/high[] flag ids, top_issues[], liquidity_usd. EVM (default base) or Solana mint. Full report: token_verdict. $0.002/call. Use for a quick, cheap buy/no-buy risk check of a token; for holders, owner, LP lock and every flag use token_verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
token_verdict Token risk verdict ~224
Before buying, sniping or routing a swap: send a token contract address (EVM: base default, ethereum, bsc, arbitrum, polygon, optimism, avalanche; or a Solana mint) and get a deterministic risk verdict — DANGER / HIGH_RISK / CAUTION / LOW_RISK with a 0–100 score and named flags: honeypot, sell/buy tax, mintable, pausable, blacklist, hidden or reclaimable owner, unverified source, proxy, holder concentration, creator share, unlocked LP, thin or brand-new liquidity. Sources: GoPlus + DexScreener, 5-min cache. $0.01/call. Use for one token contract's risk checks; not a price or a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address (0x… for EVM, base58 mint for Solana) |
| chain | string | – | base (default for 0x), ethereum, bsc, arbitrum, polygon, optimism, avalanche, solana (auto for base58) |
No output schema declared.
No examples provided.
topic_demand Topic demand (Wikipedia pageviews) ~162
Attention a subject gets now, from the official Wikimedia pageviews API: items[] {topic, article, url, views_last_day, avg_7d, change_7d_pct, avg_30d, change_30d_pct, trend rising|falling|steady, peak_60d, daily_30d[]}, ranked by avg_7d. Up to 5 topics (comma-separated), lang en/pt/es…. $0.002/call. Use to see how much attention topics get now (Wikipedia pageviews, 7d/30d change, rising or falling) before choosing what content to make.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| topics | string | yes | comma-separated, e.g. Bitcoin,Ethereum |
No output schema declared.
No examples provided.
topic_timeline Topic timeline ~141
Dated timeline of a topic from Wikidata (CC0): events[] {date, precision, event, relation, wikidata}, summary {text, url, license} from Wikipedia (CC BY-SA), interest {avg_7d_views, change_30d_pct, trend}. $0.003/call. Use to build a dated timeline of a topic (documentary, explainer, research) with sources; for audience interest alone use topic_demand.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | en, pt, es… |
| limit | integer | – | – |
| q | string | yes | e.g. Federal Reserve, Apollo 11, Ethereum |
No output schema declared.
No examples provided.
treasury_auctions U.S. Treasury auctions ~86
Recent U.S. Treasury auction results (high yield, bid-to-cover, indirect/direct/primary-dealer share) and upcoming auctions with size, from public-domain Fiscal Data. $0.003/call. Use for U.S. Treasury auction results and the upcoming calendar; for all macro releases use calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
universe Universe ~86
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. Use to list valid asset ids for other tools (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whale_moves Whale moves ~148
Large USDC/USDT transfers on Base and Ethereum from public explorers (no key): USD size, best-effort exchange labels (Binance, Coinbase, OKX, Bybit…), flow tag (to_exchange = potential sell pressure, from_exchange = withdrawal, mint/burn = stablecoin supply, wallet_to_wallet), totals by flow, tx links. Default threshold $1M. $0.002/call. Use for individual large stablecoin transfers; for total supply change use stablecoin_supply.
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | – | Default both. |
| limit | integer | – | – |
| min_usd | number | – | Minimum transfer size in USD. Default 1,000,000. |
No output schema declared.
No examples provided.
youtube_channel_growth YouTube channel growth ~79
Subscribers, views and uploads per day from Degenscan's daily snapshots, change_7d and change_30d (abs, pct), daily[]. Tracking starts on first lookup. $0.003/call. Use for a YouTube channel's subscriber and view growth over 7 and 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
No output schema declared.
No examples provided.
youtube_outliers YouTube outliers ~145
A channel's recent uploads ranked by views ÷ the channel's median (long-form and Shorts separately): channel {title, subscribers}, long/shorts {median_views, items[] {id, url, title, views, multiple_of_median, views_per_day, age_days, too_recent}}. Derived metrics from the YouTube Data API. $0.005/call. Use to find a YouTube channel's videos that did many times its normal views (outliers) to decide what content to make.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | @handle, UC… channel id or channel URL |
| format | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
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'
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.