Lens intelligence, inside your AI assistant.

You're in Claude Desktop, you've connected the Streaming Radar MCP server. You ask:

"what's mobile-money penetration in Kenya in 2025 per GSMA?"

Claude calls the silo_get_datapoints tool, fetches the value (with source, date, confidence, provenance link), and replies: "Per GSMA Mobile Economy 2025, mobile-money penetration in Kenya is 84% of adult population, December 2024 figure, high confidence. Source: Safaricom/M-Pesa + GSMA triangulation."

Same for 4,000+ Lens figures. Same for newsletter articles. Same for strategic models (P&L Africa 5 models, DCF VI, ASRI scores 15 countries, 2030 scenarios).

Claude.ai (OAuth 2.1, one click) — in Settings → Connectors → Add Custom Connector:

https://streaming-radar-mcp.streamingradar.workers.dev

OAuth 2.1 + PKCE compliant with RFC 8414. The Streaming Radar sign-in page asks for your email and sends you a 6-digit code. Once the code is verified, you are back in Claude with the tools of your access: the newsletter tier for free, the silos of your subscription if you have one. Already have an `sl_live_` key? Paste it on the same page.

Claude Desktop (JSON config file) — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{ "mcpServers": { "streaming-radar": { "command": "npx", "args": ["-y", "mcp-remote", "https://streaming-radar-mcp.streamingradar.workers.dev", "--header", "Authorization: Bearer sl_live_YOUR_KEY"] } } }

ChatGPT (Developer Mode), Plus, Pro, Business, Enterprise or Edu plans.

1. Settings → Profile, enable "Developer Mode" (beta)
2. Settings → Connectors → Add Custom Connector
3. URL: https://streaming-radar-mcp.streamingradar.workers.dev
4. Auth: OAuth 2.1 (recommended) or Bearer sl_live_YOUR_KEY
5. Confirm the requested scope
6. New chat, + button, select "Streaming Radar"

181 tools invocable in natural language. ChatGPT shows confirmation before each tool call (standard Developer Mode behavior).

ChatGPT (standard mode, Deep Research, Company Knowledge), all paid plans.

ChatGPT standard mode requires search and fetch wrappers that Streaming Radar exposes via a dedicated endpoint.

1. Settings → Connectors → Add Custom Connector
2. URL: https://streaming-radar-mcp.streamingradar.workers.dev/chatgpt
3. Auth: OAuth 2.1 or Bearer
4. The server exposes 2 tools: search (returns datapoint / article ids matching the query) and fetch (returns the full record by id)
5. Use in Deep Research or Company Knowledge without enabling Developer Mode

Limitations vs Developer Mode: no analytical models (P&L, DCF, ASRI), no admin tools. Newsletter and report datapoints in semantic read-only mode.

Microsoft Copilot (Studio, Microsoft 365). Settings → Custom connectors → MCP server, URL above, Bearer. Doc: learn.microsoft.com/copilot.

Perplexity (Pro, Enterprise). Settings → Connectors → Custom MCP, URL and auth. Doc: perplexity.ai/help-center.

Grok (Premium+). Tools → Custom MCP server, URL and auth.

Any MCP-spec compliant client works. If yours isn't listed, point it at the URL with a Bearer token.

Cursor / other MCP clients, same principle, entry point `https://streaming-radar-mcp.streamingradar.workers.dev`, Bearer auth `sl_live_`.

Direct script (curl) to test:

curl -H "Authorization: Bearer sl_live_xxx" https://streaming-radar-mcp.streamingradar.workers.dev/mcp -d '{"jsonrpc":"2.0","method":"tools/list"}'

Every page of this site declares its tools in the browser — document.modelContext, the WebMCP protocol. An agent that opens lens.streaming-radar.com discovers and calls them directly: no key, no account, no scraping. That is the free door; the MCP server above stays the door to the values.

What these tools return: the site's published content, the newsletter archive, today's market signals, the P&L model from the calculator page, and — for any subject — how many sourced datapoints exist, across which countries and years, and how recent they are. What they do not return: the values. Those sit behind the MCP server, with their source and provenance chain.

Browser requirement: Chrome 146+ with the WebMCP surface enabled. Anywhere else the tools simply do not register and the page behaves exactly as before — no side effects.

The free key opens the newsletter tools (sr_*), 100 calls a day. You create it on the sign-in page: your work email, a 6-digit code, the key shown once. The report silos open on request, after a conversation about your use (see pricing).

A Node.js Cloudflare Worker serves the 181 tools via JSON-RPC compliant with MCP spec. Auth via OAuthProvider @cloudflare/workers-oauth-provider (OAuth 2.1 + PKCE) or Bearer token SHA-256 hash matched against hub.api_keys. Rate limiting via Durable Object (60 req/min subscriber, 120 req/min admin). KV cache TTL 60–300s for read tools. Data layer Supabase Postgres, D1 edge replica for high-frequency endpoints, Vectorize 768 dims for newsletter semantic search.

Source code: MCP is proprietary, not open source. But the MCP spec (modelcontextprotocol.io) is open — everything we publish follows the official Anthropic spec.