# New-Term Radar

Spots new model, product and repo names the day they surface and maps the search terms behind them. For anyone building pages around fresh terms.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 1766
- Author: zhuyansen
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/zhuyansen/new-term-radar
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/new-term-radar

## What it does

The radar runs six signals daily: X posts, models and demos new to Hugging Face trending, GitHub repos under 14 days old averaging 200+ stars a day, new URLs in sitemaps, freshly indexed domains, and Search Console queries. It also pulls Reddit asks, sites that just added a first payment link, and products with verified revenue. Google Trends is not a source here — it is the check, run 14 days after each lead.

The package is Python and starts through `uvx`. Alongside the MCP server there are three Agent Skills and a `pains` command. Signals from X, Reddit, new domains and sellers need an AIsa key; revenue data needs a TrustMRR key; visit data takes an optional GoAnyAPI key. Without the AIsa key, part of the signals will not run.

What comes out is a keyword table: each new name gets the generic search phrases around it, a size estimate, a page-one room check and a decision. Config and state are set through `RADAR_CONFIG` and `RADAR_STATE`.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `AISA_API_KEY`, `GOANYAPI_API_KEY`, `RADAR_CONFIG`, `RADAR_STATE` — keys and tokens: ask the human for the values, never commit them or put them in shared files.
- Works with: GitHub

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env AISA_API_KEY=<AISA_API_KEY> --env GOANYAPI_API_KEY=<GOANYAPI_API_KEY> --env RADAR_CONFIG=<RADAR_CONFIG> --env RADAR_STATE=<RADAR_STATE> --transport stdio new-term-radar -- uvx new-term-radar
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from new-term-radar <command>

### Codex

**Platform CLI**
```bash
codex mcp add new-term-radar --env AISA_API_KEY=<AISA_API_KEY> --env GOANYAPI_API_KEY=<GOANYAPI_API_KEY> --env RADAR_CONFIG=<RADAR_CONFIG> --env RADAR_STATE=<RADAR_STATE> -- uvx new-term-radar
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from new-term-radar <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "new-term-radar": {
            "command": "uvx",
            "args": [
                "new-term-radar"
            ],
            "env": {
                "AISA_API_KEY": "<AISA_API_KEY>",
                "GOANYAPI_API_KEY": "<GOANYAPI_API_KEY>",
                "RADAR_CONFIG": "<RADAR_CONFIG>",
                "RADAR_STATE": "<RADAR_STATE>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from new-term-radar <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "new-term-radar": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "new-term-radar"
            ],
            "env": {
                "AISA_API_KEY": "<AISA_API_KEY>",
                "GOANYAPI_API_KEY": "<GOANYAPI_API_KEY>",
                "RADAR_CONFIG": "<RADAR_CONFIG>",
                "RADAR_STATE": "<RADAR_STATE>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from new-term-radar <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e AISA_API_KEY=<AISA_API_KEY> -e GOANYAPI_API_KEY=<GOANYAPI_API_KEY> -e RADAR_CONFIG=<RADAR_CONFIG> -e RADAR_STATE=<RADAR_STATE> new-term-radar uvx new-term-radar
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from new-term-radar <command>

## When to use it
- learn a new model name the day it appears, not two weeks later
- find the search phrases around a fresh term before keyword tools list them
- track a repo gaining stars faster than usual
- collect Reddit asks an AI tool could answer
- check whether a term held up 14 days after the first signal

## Example prompts
- Show today's new terms and the searches behind them
- Which GitHub repos are averaging 200+ stars a day?
- Run the `pains` command and collect Reddit asks about AI tools

## Similar
- [Google Maps MCP Server](https://affpapa.org/en/nevibecode/mcp/google-maps-mcp-server.md) — MCP server · ★ 479
- [squirrelscan](https://affpapa.org/en/nevibecode/mcp/squirrelscan.md) — MCP server · ★ 296
- [Tin](https://affpapa.org/en/nevibecode/mcp/tin.md) — MCP server · ★ 263
- [lighthouse-mcp](https://affpapa.org/en/nevibecode/mcp/lighthouse-mcp.md) — MCP server · ★ 212
- [SerpApi](https://affpapa.org/en/nevibecode/mcp/serpapi.md) — MCP server · ★ 182
- [Analook — Competitor Intelligence](https://affpapa.org/en/nevibecode/mcp/analook-competitor-intelligence.md) — MCP server · ★ 111

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md