# Streaming Radar (remote · mcp.streaming-lens.com)

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

- Trust score: 68/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.streaming-lens.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-streaming-lens-mcp-streaming-radar/public.md), [page](https://verifymcp.io/servers/com-streaming-lens-mcp-streaming-radar/public)

## Channel facts

- Endpoint: `https://mcp.streaming-lens.com/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-streaming-lens-mcp-streaming-radar 'https://mcp.streaming-lens.com/public'
```

### Cursor

```json
{
  "mcpServers": {
    "com-streaming-lens-mcp-streaming-radar": {
      "url": "https://mcp.streaming-lens.com/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-streaming-lens-mcp-streaming-radar": {
      "type": "http",
      "url": "https://mcp.streaming-lens.com/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-streaming-lens-mcp-streaming-radar]
url = "https://mcp.streaming-lens.com/public"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add com-streaming-lens-mcp-streaming-radar --url 'https://mcp.streaming-lens.com/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-streaming-lens-mcp-streaming-radar:
    url: "https://mcp.streaming-lens.com/public"
```

### Netclaw

```json
{
  "McpServers": {
    "com-streaming-lens-mcp-streaming-radar": {
      "Transport": "http",
      "Url": "https://mcp.streaming-lens.com/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-streaming-lens-mcp-streaming-radar -t streamable-http -u 'https://mcp.streaming-lens.com/public'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 68, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 68, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-18 (score 68, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 67, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-16 (score 67, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-15 (score 67, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-14 (score 66, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-13 (score 66, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (11)

### `check_data_coverage` (~244 tokens)

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.

Input parameters:

- `country` (string): Restrict to one country as spelled in the data (e.g. "Nigeria").
- `query` (string, required): 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").

### `sr_get_articles` (~110 tokens)

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.

Input parameters:

- `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

### `sr_get_article` (~76 tokens)

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.

Input parameters:

- `id` (string): Article UUID
- `number` (number): Edition number (e.g. 42)

### `sr_search_articles` (~331 tokens)

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.

Input parameters:

- `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, required): 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

Output parameters:

- `articles` (array)
- `count` (integer)

### `sr_get_experts` (~104 tokens)

List experts cited in the Streaming Radar newsletter with optional filters by tier or country. Free access — no API key required.

Input parameters:

- `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)

### `sr_get_tags` (~68 tokens)

List tags used in the Streaming Radar newsletter, optionally filtered by category. Free access — no API key required.

Input parameters:

- `category` (string): Tag category (e.g. "company", "country", "topic", "format")
- `limit` (number): Max results (default 50)

### `sr_get_new_since` (~91 tokens)

Get articles published since a given date, ordered by publication date descending. Free access — no API key required.

Input parameters:

- `limit` (number): Max results (default 20, max 50)
- `since_date` (string, required): ISO 8601 date or datetime (e.g. "2026-02-01" or "2026-02-01T00:00:00Z")

### `sr_get_expert` (~64 tokens)

Get a single expert by ID or name (partial match), including their linked articles. Free access — no API key required.

Input parameters:

- `id` (string): Expert UUID
- `name` (string): Expert name (partial match, e.g. "Ludovic")

### `story_list_genres` (~34 tokens)

List all available genre tiers (Proven / Growing / Emerging) and hybrid combinations for the vertical drama story bible generator.

### `story_list_markets` (~28 tokens)

List all target markets with audience profiles and top genres for the vertical drama story bible generator.

### `search_tools` (~130 tokens)

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).

Input parameters:

- `limit` (number): Max tools to return (default 8, max 20).
- `query` (string, required): Whitespace-separated keywords; case-insensitive.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-streaming-lens-mcp-streaming-radar/public#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.streaming-lens.com/public
- Website: https://lens.streaming-radar.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-streaming-lens-mcp-streaming-radar/public.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-streaming-lens-mcp-streaming-radar/public.json
- HTML version of this page: https://verifymcp.io/servers/com-streaming-lens-mcp-streaming-radar/public