mcpbeat Sign in

Streaming Radar MCP Server

by streaming-lens-mcp Your server? Claim it
answering

Streaming Radar is answering right now. Last checked 6 min ago. It exposes 12 tools.

Streaming market intelligence: vertical drama, African OTT, piracy, sports, creator economy.

Uptime history 62 days of history · worst day 92%
62 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
488 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 31

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

5 Nov a tool changed the parameters it asks for sr_search_articles
15 Oct a tool changed version3 times that day
7 Oct a tool changed version2 times that day
6 Oct a tool changed version3 times that day
5 Oct 2 tool descriptions were rewritten sr_get_article, sr_get_articles
5 Oct 2 tools changed the parameters they ask for sr_get_articles, sr_search_articles
3 Oct 2 tool descriptions were rewritten sr_get_article, sr_search_articles
3 Oct a tool changed the parameters it asks for sr_search_articles
3 Oct a tool changed version
1 Oct 2 tool descriptions were rewritten check_data_coverage, search_tools
and 17 more, back to 18 September 2026

Nothing serious here today

Today is the operative word: we check Streaming Radar every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add streaming-radar --transport http https://mcp.streaming-lens.com/public
Settings → Connectors → Add custom connector, then paste this address
https://mcp.streaming-lens.com/public
~/.codex/config.toml
[mcp_servers.streaming-radar]
url = "https://mcp.streaming-lens.com/public"
.cursor/mcp.json
{
  "mcpServers": {
    "streaming-radar": {
      "url": "https://mcp.streaming-lens.com/public"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "streaming-radar": {
      "type": "http",
      "url": "https://mcp.streaming-lens.com/public"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

articles
sr_get_articles
List Streaming Radar newsletter articles with optional filters. Returns id, number, title, subtitle, status, type, published_at, substack_url and editorial_angle; views and open_rate only with an admin key. Without an admin key only published articles are returned and any other status filter is rejected. Free access — no API key required.
sr_search_articles
Search Streaming Radar articles, or — with mode=coverage — check whether a topic is already covered in the published corpus using semantic similarity. mode=search (default): case-insensitive whole-query substring match on article metadata, plus indexed full-text search of published piece bodies. Multi-word body queries require all terms. Use short queries for names. Free access, no API key required. mode=coverage: semantic anti-redite + auto-citation check over the published corpus. Returns a channel-weighted verdict (DÉJÀ TRAITÉ / EFFLEURÉ / NEUF — only PUBLISHED pieces can block; briefs are non-blocking signals), plus citable hits (url + excerpt) for self-citation. Also returns a facts array: passages already published in the body of a piece that carry the same rare terms as the query (non-blocking). Free access.
story
story_list_genres
List all available genre tiers (Proven / Growing / Emerging) and hybrid combinations for the vertical drama story bible generator.
story_list_markets
List all target markets with audience profiles and top genres for the vertical drama story bible generator.
article
sr_get_article
Get a Streaming Radar article by sr_articles ID, published_pieces ID, or edition number. Returns the published body when available; internal briefs return metadata only. Without an admin key only published articles resolve; any other article returns "Article not found". Free access — no API key required.
chart
get_chart_data
Get chart-ready data for Plotly or any charting library. Report charts require auth. Newsletter charts (expert_network, topic_heatmap, engagement_funnel, geo_coverage, keyword_trends, article_bridge, expert_leaderboard, timeline) are available without signing in.
data
check_data_coverage
Check what sourced data Streaming Lens holds on a company, market, country or topic — WITHOUT returning the values. Returns how many datapoints match, which reports they sit in, which countries and years they cover, the confidence mix, when the most recent one was updated, and one sample datapoint with its metric name, unit, country, source and confidence but its value withheld. Use this to tell a user whether the answer to their question exists in the database and what it would take to read it. Matching is word-bounded, so short acronyms do not match inside longer words. Free access — no API key required. Read-only: it never returns the values, and the response says which reports hold them.
expert
sr_get_expert
Get a single expert by ID or name (partial match), including their linked articles. Free access — no API key required.
experts
sr_get_experts
List experts cited in the Streaming Radar newsletter with optional filters by tier or country. Free access — no API key required.
new
sr_get_new_since
Get published articles since a given date, ordered by publication date descending. Only published articles are returned. Free access — no API key required; the views and open_rate fields are returned only with an admin key.
tags
sr_get_tags
List tags used in the Streaming Radar newsletter, optionally filtered by category. Free access — no API key required.
tools
search_tools
Search the tools available to your account by keyword. Returns matching tools with their names, descriptions and input schemas: the same tools tools/list advertises to you, nothing more. Use it to find which tool fits a request. Keywords can be: a tool name fragment (e.g. "chart"), a domain (africa, vertical, piracy, creator, sports), or an action (list, get, compare).

Endpoints

URLTransportStateLatencyChecked
https://mcp.streaming-lens.com/public streamable-http answering 461 ms 6 min ago

Alternatives to Streaming Radar

same job, measured the same way
Draconic Market Intelligence
by draconic

Live multi-signal market intelligence for supported instruments. Analysis only.

answering
OmniSignal
by omnisignal

Live market intelligence & AI content strategy: trends, competitor moves, content calendar.

answering
Degenscan Intel
by tradewr333-lgtm

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

73 tools answering
P
PreFlyte — DeFi Financial Intelligence for AI Agents
by preflyte

Evidence-based market data for AI agents deploying capital in DeFi. Empirical, not advertised.

9 tools answering
AIXBT
by aixbt

Crypto market intelligence for Projects, Topics, Intel, Reports, and Clusters.

12 tools answering
Cryptodata MCP
by kota1026

CryptoData MCP Server - Real-time crypto market data, DeFi analytics, and on-chain intelligence...

51 installs/wk local only
CriptoNous
by criptonous-app

Crypto market intelligence for AI agents: sentiment, flow, Oracle readings. x402. NFA.

9 tools answering
Newsgurus Intel
by collectorguru

Pay-per-call trading intelligence for AI agents: live market regime, trading signals, composite conv

46 tools answering

Streaming Radar — questions

Answers built from our own checks of this server.

What can Streaming Radar do?
It exposes 12 tools, read directly from the server on our last check. Among them: check_data_coverage, get_chart_data, search_tools, sr_get_article, sr_get_articles, sr_get_expert and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Streaming Radar mostly used for?
Its tools cluster around articles and story. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Streaming Radar working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 488 ms. The bar chart above shows every period we have measured.
How do I connect Streaming Radar?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Streaming Radar need an API key?
No. Streaming Radar completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Streaming Radar?
It answers our handshake in 488 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.