Remote MCP · Endpoint
Name.ai MCP Server MCP server
No. Name.ai MCP Server answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.name.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.name/nameai-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 146 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.
- Website
- https://name.ai/developers
- Repository
- https://github.com/namekart/nameai_mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 146 ms |
| 1 day ago | Handshake completed | 172 ms |
| 3 days ago | Handshake completed | 165 ms |
| 3 days ago | Handshake completed | 165 ms |
| 4 days ago | Handshake completed | 170 ms |
| 5 days ago | Handshake completed | 204 ms |
| 7 days ago | Handshake completed | 186 ms |
| 10 days ago | Handshake completed | 156 ms |
| 12 days ago | Handshake completed | 355 ms |
| 15 days ago | Handshake completed | 317 ms |
| 17 days ago | Handshake completed | 296 ms |
| 19 days ago | Handshake completed | 299 ms |
| 21 days ago | Handshake completed | 322 ms |
| 23 days ago | Handshake completed | 303 ms |
| 25 days ago | Handshake completed | 298 ms |
| 26 days ago | Handshake completed | 308 ms |
| 28 days ago | Handshake completed | 300 ms |
| 29 days ago | Handshake completed | 302 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Name.ai MCP Server and makes no claim about it beyond what these checks measured.