We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

New-Term Radar

MCP server by zhuyansen

Catch new AI model, product and repo names as they surface, with the search terms behind them sized.

Runs locally (Runs on your machine: its page has the install command)Runs with uvxNeeds an API key

Install New-Term Radar

Runs on your machine. Your client starts it with this command:

uvx --with mcp new-term-radar mcp

Needs uv (Python) on your computer. The setup steps below show where the command goes in each client.

  • AISA_API_KEY secret AIsa key. X posts, search volumes, Google Trends and the models all go through it.
  • GOANYAPI_API_KEY secret optional Optional. Adds what people searched together with each name, and one country's settled daily series.
  • RADAR_CONFIG optional Optional. Absolute path to your config.json (X accounts, sitemaps, thresholds).
  • RADAR_STATE optional Optional. Absolute path to the directory that holds the radar's SQLite state.

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/new-term-radar

About

New-Term Radar tracks names that are starting to surge in AI: new models, products, tools and repos. It reads X accounts, Hugging Face trending, fast-growing GitHub repos, directory sitemaps, new domains and Reddit asks, then builds a keyword table with estimated searches, Google Trends shape and a decision per row.

It runs locally over stdio as the PyPI package new-term-radar, started with uvx. An AIsa API key (AISA_API_KEY) is required, since X posts, search volumes, Trends and the models go through it. A GoAnyAPI key is optional and adds related queries.

What you can do

  • Detect new AI names first used on watched X accounts
  • Spot models and Spaces newly trending on Hugging Face
  • Flag GitHub repos breaking out under 14 days old
  • Find shared new words across directory sitemaps
  • Build a keyword table with search volume and Trends data
  • Check page-one competition for chosen keywords

Tools

New-Term Radar lists its tools only to clients with a key, so we can’t show them here.

Example prompts

  • Run the radar and show today's new AI names

  • Which new GitHub repos are breaking out this week?

  • Build the keyword table for the new names found today

  • What are people asking for on Reddit that an AI tool could answer?

Set up

Every client starts New-Term Radar on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio new-term-radar --env "AISA_API_KEY=<YOUR_AISA_API_KEY>" --env "GOANYAPI_API_KEY=<YOUR_GOANYAPI_API_KEY>" -- uvx --with mcp new-term-radar mcp
  1. Start Claude Code and type /mcp. new-term-radar should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "new-term-radar": {
      "command": "uvx",
      "args": [
        "--with",
        "mcp",
        "new-term-radar",
        "mcp"
      ],
      "env": {
        "AISA_API_KEY": "<YOUR_AISA_API_KEY>",
        "GOANYAPI_API_KEY": "<YOUR_GOANYAPI_API_KEY>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "new-term-radar": {
      "command": "uvx",
      "args": [
        "--with",
        "mcp",
        "new-term-radar",
        "mcp"
      ],
      "env": {
        "AISA_API_KEY": "<YOUR_AISA_API_KEY>",
        "GOANYAPI_API_KEY": "<YOUR_GOANYAPI_API_KEY>"
      }
    }
  }
}

Needs uv (Python) on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "new-term-radar": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--with",
        "mcp",
        "new-term-radar",
        "mcp"
      ],
      "env": {
        "AISA_API_KEY": "${input:aisa-api-key}",
        "GOANYAPI_API_KEY": "${input:goanyapi-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "aisa-api-key",
      "description": "AISA_API_KEY",
      "password": true
    },
    {
      "type": "promptString",
      "id": "goanyapi-api-key",
      "description": "GOANYAPI_API_KEY",
      "password": true
    }
  ]
}

Needs uv (Python) on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "new-term-radar": {
      "command": "uvx",
      "args": [
        "--with",
        "mcp",
        "new-term-radar",
        "mcp"
      ],
      "env": {
        "AISA_API_KEY": "<YOUR_AISA_API_KEY>",
        "GOANYAPI_API_KEY": "<YOUR_GOANYAPI_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add new-term-radar --env "AISA_API_KEY=<YOUR_AISA_API_KEY>" --env "GOANYAPI_API_KEY=<YOUR_GOANYAPI_API_KEY>" -- uvx --with mcp new-term-radar mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.new-term-radar]
command = "uvx"
args = ["--with", "mcp", "new-term-radar", "mcp"]
env = { AISA_API_KEY = "<YOUR_AISA_API_KEY>", GOANYAPI_API_KEY = "<YOUR_GOANYAPI_API_KEY>" }

Needs uv (Python) on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "AISA_API_KEY=<YOUR_AISA_API_KEY>" -e "GOANYAPI_API_KEY=<YOUR_GOANYAPI_API_KEY>" new-term-radar uvx -- --with mcp new-term-radar mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "new-term-radar": {
      "command": "uvx",
      "args": [
        "--with",
        "mcp",
        "new-term-radar",
        "mcp"
      ],
      "env": {
        "AISA_API_KEY": "<YOUR_AISA_API_KEY>",
        "GOANYAPI_API_KEY": "<YOUR_GOANYAPI_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs uv (Python) on your computer. Replace the placeholders with your own values.

Embed

Show New-Term Radar in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![New-Term Radar on mcp.tc](https://mcp.tc/i/new-term-radar/badge.svg)](https://mcp.tc/i/new-term-radar)
HTML
<a href="https://mcp.tc/i/new-term-radar"><img src="https://mcp.tc/i/new-term-radar/badge.svg" alt="New-Term Radar on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/new-term-radar.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/new-term-radar" title="New-Term Radar on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/new-term-radar.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the New-Term Radar card to your site.

Markdown
Add the mcp.tc card for New-Term Radar, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/new-term-radar.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="new-term-radar"><a href="https://mcp.tc/i/new-term-radar">New-Term Radar on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![New-Term Radar on mcp.tc](https://mcp.tc/i/new-term-radar/badge.svg)](https://mcp.tc/i/new-term-radar)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its PyPI package: each new version shows up here, with edits by its owner.

Follow New-Term Radar and we’ll email you when something changes.

  1. , Automatic check

    New version 0.6.1 (was 0.6.0). Read from PyPI.

  2. , Automatic check

    New version 0.6.0 (was 0.5.2). Read from PyPI.

  3. , Automatic check

    New version 0.5.1 (was 0.5.0). Read from PyPI.

  4. , Automatic check

    New version 0.5.0 (was 0.4.0). Read from PyPI.

  5. , Automatic check

    Tracking started: version 0.4.0.

FAQ

Can I paste mcp.tc/i/new-term-radar into my MCP client?

No. New-Term Radar runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx --with mcp new-term-radar mcp.

Does New-Term Radar need an API key?

Yes. It reads AISA_API_KEY and GOANYAPI_API_KEY from its environment, and AISA_API_KEY and GOANYAPI_API_KEY are secrets. Put the values in your client’s config on your own machine, never in a shared file.

Is New-Term Radar a remote or a local server?

Local. Your client starts it as a process on your computer with uvx --with mcp new-term-radar mcp, which needs uv (Python).

What can New-Term Radar do?

You can detect new AI names first used on watched X accounts, spot models and Spaces newly trending on Hugging Face and flag GitHub repos breaking out under 14 days old.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to New-Term Radar?

Partly. It runs on your computer, so we follow its PyPI package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read New-Term Radar’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with zhuyansen. This page was built from New-Term Radar’s public metadata, last checked on 18 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.