New Site Radar

npx add-mcp 'https://newsiteradar.com/api/mcp'

MCP access

Ask your AI assistant about new AI tool sites without leaving the editor. New Site Radar runs a remote MCP server with 7 read-only tools over the same data as the site — every answer states its data month and how the numbers were made.

Listed on Smithery and in the official MCP Registry as com.newsiteradar/new-site-radar.

Set up in three steps

1. Get a key. A free key needs no account and allows 20 tool calls a day: Get a free keyNo account, no email. 20 tool calls a day. With Pro there is no daily cap: create keys under Account → API keys (up to 3; each is shown once).
2. Point your client at https://newsiteradar.com/api/mcp with the header Authorization: Bearer nsr_… or x-api-key: nsr_… (either one; Streamable HTTP transport).
3. Ask a question — the assistant picks the tool.

Claude Code

Run in a terminal:

claude mcp add --transport http newsiteradar https://newsiteradar.com/api/mcp \
  --header "Authorization: Bearer nsr_YOUR_KEY"

Cursor

Add to ~/.cursor/mcp.json (or.cursor/mcp.json in a project):

{
  "mcpServers": {
    "newsiteradar": {
      "url": "https://newsiteradar.com/api/mcp",
      "headers": {
        "Authorization": "Bearer nsr_YOUR_KEY"
      }
    }
  }
}

Codex

Add to ~/.codex/config.toml, then export NSR_API_KEY=nsr_… in your shell:

[mcp_servers.newsiteradar]
url = "https://newsiteradar.com/api/mcp"
bearer_token_env_var = "NSR_API_KEY"

Other clients and directories (x-api-key)

If your client or MCP host cannot set the Authorization header (Smithery, for example), send the key as x-api-key instead:

{
  "mcpServers": {
    "newsiteradar": {
      "url": "https://newsiteradar.com/api/mcp",
      "headers": {
        "x-api-key": "nsr_YOUR_KEY"
      }
    }
  }
}

Tools

• search_sites — Search the current monthly board of new AI tool sites by keyword (domain / name / description) and filters (category, site type, monthly-visits bucket, MoM bucket, payment detected). Returns board rows with visits, MoM, organic share, DR, registration date and confidence. Use list_categories for valid category slugs. Arguments: query, category, type, visits, mom, payment, limit.
• get_site — Everything we have on one tracked site: monthly traffic history, channels, top countries, engagement, keywords, backlinks/DR, tech stack, payment providers with fingerprint evidence, pricing, estimated revenue range and grade, cross-check verdict, AI take (who it helps, why it wins, red flags) and competitors. Arguments: domain.
• top_rising — The top N of this month's rising-sites board (ordered by absolute monthly-visit growth), optionally within one category. Arguments: category, limit.
• revenue_signals — Top N sites on the revenue-signals board: payment provider detected (Stripe, Paddle, Lemon Squeezy …), main price, estimated monthly revenue range (USD) and grade A/B. Optional category and payment-provider filters. Arguments: category, provider, limit.
• list_categories — Category slugs on the current board (with site counts), plus the valid values for search_sites filters (type, visits, mom, payment).
• model_releases — Newest AI model releases from 26 labs (official announcements, blogs, open-weights repos), optionally by company and since a date. Arguments: company, since, limit.
• get_methodology — How the boards are built: data sources, listing thresholds, cross-check bands, confidence and revenue grades, update cadence.

Things to ask

• “Use New Site Radar: which AI video sites are rising fastest this month?”
• “Find AI sites under 50K monthly visits that already take payments.”
• “Get the details for <domain> — traffic channels, tech stack and revenue estimate.”
• “Which sites on the revenue board use Lemon Squeezy, and what do they charge?”
• “What did Anthropic and OpenAI release since 2026-09-01?”

Plans and limits

• Connecting and listing the tools is free and needs no key — that is how MCP directories and clients discover the server. Calling a tool needs a key: without one a tool call returns 401.
• A free key (nsr_free_…, from the button above) allows 20 tool calls per UTC day; the next call gets 429 until the day resets. A Pro key ($19/month or $149/year) has no daily cap. A key from an account whose Pro has ended returns 403.
• Each key may make 1 tool call every 5 seconds. Faster calls get 429 with a Retry-After header (seconds). Connecting and listing tools do not count.
• Requests without a key are limited to 30 per minute per IP address (429 with Retry-After beyond that).
• A wrong or revoked key gets 401 on any request. Revoking a key in your account takes effect immediately. Sending both headers with different keys gets 400.
• Answers are capped in size; ask for fewer rows or add filters if a result says it was truncated.
• The data is the same monthly snapshot as the boards, with the same rules — see the methodology.