Skip to main content
Glama
xbhog

namebeta-mcp

by xbhog
README.md
# namebeta-mcp

Open-source [Cursor](https://cursor.com) MCP server and agent skill for [NameBeta](https://namebeta.com).

Type a keyword in chat (`google flow video`, `chiikawa characters`). The agent looks up every NameBeta list suffix, then **probes each registered domain** to see whether a real website is deployed — parking pages do not count.

注册了你还得给我检查一下是否部署网站了

## What’s in the repo

| Path | Role |
|---|---|
| `src/` | MCP server (`lookup_domain`) and CLI |
| `.cursor/skills/namebeta-lookup/` | Cursor skill: lookup workflow + site probe |
| `.cursor/skills/namebeta-lookup/scripts/probe-sites.mjs` | HTTPS/HTTP + DNS probe; classifies live / parked / unreachable |

## Requirements

- Node.js 18+
- Cursor with MCP enabled

## Install the MCP

```bash
git clone https://github.com/xbhog/namebeta-mcp.git
cd namebeta-mcp
npm install
```

In Cursor MCP settings (or `.cursor/mcp.json`):

```json
{
  "mcpServers": {
    "namebeta": {
      "command": "node",
      "args": ["C:/absolute/path/to/namebeta-mcp/src/index.js"]
    }
  }
}
```

Then send a keyword in chat. The tool maps `"google flow video"` → `googleflowvideo.com` and queries [namebeta.com/search/googleflowvideo.com](https://namebeta.com/search/googleflowvideo.com).

## Install the skill

Copy the skill folder so Cursor can auto-load it:

```bash
cp -r .cursor/skills/namebeta-lookup ~/.cursor/skills/namebeta-lookup
```

On Windows (PowerShell):

```powershell
Copy-Item -Recurse .cursor\skills\namebeta-lookup $HOME\.cursor\skills\namebeta-lookup
```

The skill tells the agent: after NameBeta returns registered domains, run the probe script and report whether each hostname opens and whether a site is actually deployed.

## CLI

```bash
npm run lookup -- "google flow video"
```

Probe registered domains yourself:

```bash
node .cursor/skills/namebeta-lookup/scripts/probe-sites.mjs example.com example.net
```

JSON fields: `deployed` (true only for a live site), `kind` (`live` / `parked` / `coming_soon` / `empty` / `redirect` / `unreachable` / `error`), HTTP status, title, DNS.

## License

[MIT](LICENSE)

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of overlap or confusion. The tool's purpose is unique by default.

Naming Consistency5/5

The single tool uses a clear verb_noun pattern (lookup_domain), establishing a consistent convention even with an isolated example.

Tool Count2/5

A single tool is minimal for a server; while the tool is non-trivial and well-scoped, the server feels incomplete for broad use cases like domain search or management.

Completeness4/5

For a pure lookup service, the tool covers the core workflow well (search, availability, registration details). However, adjacent operations like domain suggestions or WHOIS history are absent, leaving minor gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues