Content Tools
streaming-radar.com
Provides tools to browse, search, and retrieve Streaming Radar newsletter articles and cited experts, and to check topic coverage in the published corpus.
ENDPOINT 1
https://mcp.streaming-lens.com/public
MCP server metadata
- Name
- streaming-radar-mcp
- Version
- 1.4.0
Avant de proposer un angle, un plan ou un titre pour un contenu Streaming Radar (article Substack, LinkedIn story, post LinkedIn), appeler D'ABORD sr_search_articles en mode "coverage" avec l'angle envisagé en texte libre, et présenter le verdict d'antériorité (DÉJÀ TRAITÉ / EFFLEURÉ / NEUF) AVANT toute proposition. Réutiliser les hits comme matière d'auto-citation (url + extrait) quand c'est pertinent.
Known tools 11
check_data_coverageCheck what sourced data Streaming Lens holds on a company, market, country or topic — WITHOUT returning the values.
Inferred read-onlysr_get_articleGet a single Streaming Radar article by ID or edition number, including full content, linked experts, and editorial angle.
Inferred read-onlysr_search_articlesFull-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).
Inferred read-onlysr_get_expertsList experts cited in the Streaming Radar newsletter with optional filters by tier or country.
Inferred read-onlysr_get_tagsList tags used in the Streaming Radar newsletter, optionally filtered by category.
Inferred read-onlysr_get_new_sinceGet articles published since a given date, ordered by publication date descending.
Inferred read-onlysr_get_expertGet a single expert by ID or name (partial match), including their linked articles.
Inferred read-onlystory_list_genresList all available genre tiers (Proven / Growing / Emerging) and hybrid combinations for the vertical drama story bible generator.
Inferred read-onlystory_list_marketsList all target markets with audience profiles and top genres for the vertical drama story bible generator.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.streaming-radar-mcp]
url = "https://mcp.streaming-lens.com/public"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"streaming-radar-mcp": {
"type": "http",
"url": "https://mcp.streaming-lens.com/public"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: streaming-radar-mcp
Remote MCP URL: https://mcp.streaming-lens.com/public
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"streaming-radar-mcp": {
"url": "https://mcp.streaming-lens.com/public"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"streaming-radar-mcp": {
"type": "http",
"url": "https://mcp.streaming-lens.com/public"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "streaming-radar-mcp",
"transport": "streamable-http",
"url": "https://mcp.streaming-lens.com/public"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.