Nameshift: MCP server, CLI and agent surfaces
Not verified. A source lists an MCP endpoint for Nameshift (api.nameshift.com), but it did not answer a handshake on 4 November 2026, so it is not counted. The connector recorded: no MCP answer (POST HTTP 404, GET HTTP 404 application/json; charset=utf-8).
Fact sheet
| Company | Nameshift (registry title: nameshift.com) |
|---|
| Domain | nameshift.com |
|---|
| Category | Agent Tools (assigned by this directory from the registry description) |
|---|
| MCP server | No answer |
|---|
| Tranco rank | 5,460 on the list of 4 November 2026 |
|---|
| Ora score | none: Ora returned no cached score for nameshift.com when asked on 5 November 2026 |
|---|
| Company found through | the official MCP Registry |
|---|
| Last verified | 4 November 2026 |
|---|
MCP server
| Endpoint | https://api.nameshift.com/mcp |
|---|
| How it was found | listed in the official MCP Registry |
|---|
| HTTP status | 404 |
|---|
| Connected | 4 November 2026, 20:01 UTC |
|---|
| Handshake time | 332 ms over 2 attempts |
|---|
| Result | no MCP answer (POST HTTP 404, GET HTTP 404 application/json; charset=utf-8) |
|---|
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:56:07Z https://api.nameshift.com/mcp sent initialize result no-answer (HTTP 404) 324 ms
- 20:01:45Z https://api.nameshift.com/mcp sent initialize result no-answer (HTTP 404) 332 ms
Authentication
| Auth type | Auth not determined |
|---|
The sign-in route, step by step
- Request
https://api.nameshift.com/mcp. The connector could not tell what it wants: no MCP answer (POST HTTP 404, GET HTTP 404 application/json; charset=utf-8). - Check the vendor's docs for the sign-in route before wiring a client.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for Nameshift. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
Agent surfaces other than MCP and CLI| Surface | Result |
|---|
| OpenAPI file | No OpenAPI file at the root paths checked. |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | Not found (the crawl got a non-200 answer). |
| A2A agent card | Not found (the crawl got a non-200 answer). |
| A2A agent card (older path) | Not found (the crawl got a non-200 answer). |
| agents.json | Not found (the crawl got a non-200 answer). |
| OAuth authorization server metadata | Not found (the crawl got a non-200 answer). |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
Registry listings| Registry | Listed |
|---|
| Official MCP Registry | Yes: com.nameshift/marketplace |
| GitHub MCP Registry | No |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |