Streaming Radar
REMOTE · MCP.STREAMING-LENS.COM · SCANNED SEP 20
Streaming market intelligence: vertical drama, African OTT, piracy, sports, creator economy.
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1389 tokens (~126/item across 11 items; 11 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Streaming Radar MCP server?
Streaming Radar is a hosted endpoint at https://mcp.streaming-lens.com/public, 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 · mcp.streaming-lens.com
claude mcp add --transport http com-streaming-lens-mcp-streaming-radar 'https://mcp.streaming-lens.com/public'
{
"mcpServers": {
"com-streaming-lens-mcp-streaming-radar": {
"url": "https://mcp.streaming-lens.com/public"
}
}
} {
"servers": {
"com-streaming-lens-mcp-streaming-radar": {
"type": "http",
"url": "https://mcp.streaming-lens.com/public"
}
}
} [mcp_servers.com-streaming-lens-mcp-streaming-radar] url = "https://mcp.streaming-lens.com/public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-streaming-lens-mcp-streaming-radar": {
"type": "remote",
"url": "https://mcp.streaming-lens.com/public",
"enabled": true
}
}
} openclaw mcp add com-streaming-lens-mcp-streaming-radar --url 'https://mcp.streaming-lens.com/public' --transport streamable-http
mcp_servers:
com-streaming-lens-mcp-streaming-radar:
url: "https://mcp.streaming-lens.com/public" {
"McpServers": {
"com-streaming-lens-mcp-streaming-radar": {
"Transport": "http",
"Url": "https://mcp.streaming-lens.com/public"
}
}
} assistant mcp add com-streaming-lens-mcp-streaming-radar -t streamable-http -u 'https://mcp.streaming-lens.com/public'
{
"mcpServers": {
"com-streaming-lens-mcp-streaming-radar": {
"type": "http",
"url": "https://mcp.streaming-lens.com/public"
}
}
} 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.
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 20 Sept 2026 · Probed https://mcp.streaming-lens.com/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=streaming-lens.com | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2f8e9db3514fa8330e1cbd2fe276d369 |
| SANs: streaming-lens.com, mcp.streaming-lens.com, *.mcp.streaming-lens.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 mcp.streaming-lens.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| streaming-lens.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://mcp.streaming-lens.com/public | Verified | 200 | |
| http (plaintext) | http://mcp.streaming-lens.com/public | Served over HTTP | 200 |
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 →
check_data_coverage ~244
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. The values themselves are behind the paid MCP server; the response says where.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Restrict to one country as spelled in the data (e.g. "Nigeria"). |
| query | string | yes | Company, market, country, platform or topic (e.g. "ReelShort", "mobile money", "Nigeria", "micro-drama"). |
| report_slug | string | – | Restrict to one report silo (e.g. "vertical-invasion-2026", "africa-streaming-2026"). |
Structured output declared, but exposes no named fields.
No examples provided.
search_tools ~130
Search the full MCP catalog for tools not in the core set. Returns matching tools with their full schemas, ready to call via tools/call. Use when the user request maps to a capability not in the core set. Keywords can be: tool name fragment (e.g. "ingest_bulk"), domain (africa, vi, piracy, ce, sports, crm, admin), or action (list, get, create, compare).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max tools to return (default 8, max 20). |
| query | string | yes | Whitespace-separated keywords; case-insensitive. |
Structured output declared, but exposes no named fields.
No examples provided.
sr_get_article ~76
Get a single Streaming Radar article by ID or edition number, including content_markdown when the full body exists in hub.published_pieces, linked experts, and editorial angle. Free access — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Article UUID |
| number | number | – | Edition number (e.g. 42) |
Structured output declared, but exposes no named fields.
No examples provided.
sr_get_articles ~110
List Streaming Radar newsletter articles with optional filters. Returns title, subtitle, status, type, views, open_rate, editorial_angle, and clickable links. Free access — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20, max 50) |
| offset | number | – | Pagination offset (default 0) |
| status | string | – | Filter by status: published, draft, archived |
| type | string | – | Filter by content type: edition, analysis, special |
Structured output declared, but exposes no named fields.
No examples provided.
sr_get_expert ~64
Get a single expert by ID or name (partial match), including their linked articles. Free access — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Expert UUID |
| name | string | – | Expert name (partial match, e.g. "Ludovic") |
Structured output declared, but exposes no named fields.
No examples provided.
sr_get_experts ~104
List experts cited in the Streaming Radar newsletter with optional filters by tier or country. Free access — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. "NG", "KE", "ZA") |
| limit | number | – | Max results (default 20, max 50) |
| tier | number | – | Expert tier (1 = top, 2 = mid, 3 = emerging) |
Structured output declared, but exposes no named fields.
No examples provided.
sr_get_new_since ~91
Get articles published since a given date, ordered by publication date descending. Free access — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20, max 50) |
| since_date | string | yes | ISO 8601 date or datetime (e.g. "2026-02-01" or "2026-02-01T00:00:00Z") |
Structured output declared, but exposes no named fields.
No examples provided.
sr_get_tags ~68
List tags used in the Streaming Radar newsletter, optionally filtered by category. Free access — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Tag category (e.g. "company", "country", "topic", "format") |
| limit | number | – | Max results (default 50) |
Structured output declared, but exposes no named fields.
No examples provided.
sr_search_articles ~331
Full-text search across Streaming Radar articles, or — with mode=coverage — check whether a topic is already covered in the published corpus using semantic similarity (SR_CORPUS Vectorize index). mode=search (default): full-text search on title, subtitle, editorial_angle. Free access, no API key required. mode=coverage: semantic anti-redite + auto-citation check via vector similarity 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, but they must be cited rather than re-announced as news. Requires SR_CORPUS and Workers AI. Free access.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | mode=coverage only — restrict to channels (substack, linkedin_story, linkedin_post, brief). Default: all. |
| limit | number | – | Max results (default 10, max 30) — mode=search only |
| mode | string | – | search (default) = full-text search | coverage = semantic corpus coverage check |
| query | string | yes | Search terms or topic to check coverage for (e.g. "Netflix Africa", "Canal+") |
| top_k | number | – | Number of vector neighbours to retrieve (default 10, max 30) — mode=coverage only |
| Name | Type | Req | Description |
|---|---|---|---|
| articles | array | – | – |
| count | integer | – | – |
No examples provided.
story_list_genres ~34
List all available genre tiers (Proven / Growing / Emerging) and hybrid combinations for the vertical drama story bible generator.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
story_list_markets ~28
List all target markets with audience profiles and top genres for the vertical drama story bible generator.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the Streaming Radar MCP server?
Streaming Radar is an MCP server listed in the public MCP registry as com.streaming-lens.mcp/streaming-radar. Streaming market intelligence: vertical drama, African OTT, piracy, sports, creator economy. This page covers its hosted endpoint (https://mcp.streaming-lens.com/public).
Is the Streaming Radar MCP server safe to use?
Streaming Radar scores 68 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 Streaming Radar MCP server expose?
Streaming Radar exposes 11 tools: check_data_coverage, sr_get_articles, sr_get_article, sr_search_articles, sr_get_experts, and 6 more. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.
Does the Streaming Radar MCP server require authentication?
No. We connected to Streaming Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Streaming Radar MCP server still maintained?
Streaming Radar is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.