Remote MCP · Endpoint

NameHound MCP server

No. NameHound answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
315 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 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 hour agoHandshake completed315 ms
11 hours agoHandshake completed191 ms
1 day agoHandshake completed238 ms
2 days agoHandshake completed193 ms
4 days agoHandshake completed395 ms
7 days agoHandshake completed200 ms
9 days agoHandshake completed169 ms
12 days agoHandshake completed245 ms
14 days agoHandshake completed441 ms
16 days agoHandshake completed173 ms
18 days agoHandshake completed187 ms
20 days agoHandshake completed277 ms
22 days agoHandshake completed206 ms
23 days agoHandshake completed229 ms

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

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.