Remote MCP · Endpoint

NameHound MCP server

No. NameHound answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://namehound.app/mcp

The last check completed an MCP handshake.

Registry name
app.namehound/namehound
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
231 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Is a brand name free as a .com/.net/.org/.app domain and as a Bluesky, Mastodon, npm or PyPI handle?
Listing
From the official MCP registry (active).
Recent checks of NameHound
CheckedResultHandshake
1 day agoHandshake completed231 ms
5 days agoHandshake completed484 ms
16 days agoHandshake completed176 ms
16 days agoHandshake completed250 ms
17 days agoHandshake completed265 ms
19 days agoHandshake completed169 ms
20 days agoHandshake completed315 ms
20 days agoHandshake completed191 ms
21 days agoHandshake completed238 ms
23 days agoHandshake completed193 ms
24 days agoHandshake completed395 ms
27 days agoHandshake completed200 ms
30 days agoHandshake completed169 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 20 responding of 20.

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 NameHound and makes no claim about it beyond what these checks measured.