Ext Ops Panel
Open dashboard
Comparison

io.github.kody-w/raptr-names vs io.github.ziggythebot/namecheap

io.github.kody-w/raptr-names is an MCP server published by kody-w. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ziggythebot/namecheap is an MCP server published by ziggythebot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.kody-w/raptr-namesio.github.ziggythebot/namecheap
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.3
Downloads/month (npm): 220
Downloads/week (npm): 37
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.kody-w/raptr-names vs io.github.ziggythebot/namecheap
Factio.github.kody-w/raptr-namesio.github.ziggythebot/namecheap
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (airaptr-api.azurewebsites.net/names/mcp)On your machine (@birdmania1/namecheap-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/kody-w/airaptrgithub.com/ziggythebot/namecheap-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 20 h agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.kody-w/raptr-names

In its own words, on Official MCP Registry:

Name a business or project; check which domains and GitHub names are free, with prices.

io.github.ziggythebot/namecheap

In its own words, on Official MCP Registry:

Check domain availability across 600+ TLDs on Namecheap with pricing and purchase links

How to run each

io.github.kody-w/raptr-names As a remote MCP server

Claude Code
claude mcp add --transport http raptr-names https://airaptr-api.azurewebsites.net/names/mcp

io.github.ziggythebot/namecheap As a local MCP server: npm package

Claude Code
claude mcp add --env "NAMECHEAP_API_KEY=<YOUR_NAMECHEAP_API_KEY>" --env "NAMECHEAP_API_USER=<YOUR_NAMECHEAP_API_USER>" --env "NAMECHEAP_CLIENT_IP=<YOUR_NAMECHEAP_CLIENT_IP>" --env "NAMECHEAP_USERNAME=<YOUR_NAMECHEAP_USERNAME>" --transport stdio namecheap -- npx -y @birdmania1/namecheap-mcp

Requires: NAMECHEAP_API_KEY (secret), NAMECHEAP_API_USER, NAMECHEAP_CLIENT_IP, NAMECHEAP_USERNAME

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.kody-w/raptr-names has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.kody-w/raptr-names publish no settings it asks for, so we do not compare settings.

What it can do: io.github.kody-w/raptr-names · What it can do: io.github.ziggythebot/namecheap · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built