Remote MCP · Endpoint

Startup Name Check MCP server

Yes, as of 4 hours ago: the server returned an HTTP error.

DownLast checked 4 hours ago

Server URL

https://names.openkrill.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
app.openkrill/names
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Check whether the domain for a startup, product or business name is already registered.
Listing
From the official MCP registry (active).
Recent checks of Startup Name Check
CheckedResultHandshake
4 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed195 ms
5 days agoHandshake completed425 ms
7 days agoHandshake completed215 ms
9 days agoHandshake completed155 ms
11 days agoHandshake completed229 ms
13 days agoHandshake completed108 ms
15 days agoHandshake completed912 ms
17 days agoHandshake completed85 ms
18 days agoHandshake completed57 ms
20 days agoHandshake completed312 ms
21 days agoHandshake completed35 ms
23 days agoHandshake completed50 ms

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

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