Remote MCP · Endpoint

Wellknown MCP server

No. Wellknown answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://wellknownhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.wellknownhq/wellknown
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
637 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Check whether AI agents can discover, validate, and trust your domain's services.
Listing
From the official MCP registry (active).
Recent checks of Wellknown
CheckedResultHandshake
1 hour agoHandshake completed637 ms
2 days agoHandshake completed635 ms
4 days agoHandshake completed645 ms
5 days agoHandshake completed624 ms
7 days agoHandshake completed628 ms
8 days agoHandshake completed641 ms
9 days agoHandshake completed644 ms
12 days agoHandshake completed681 ms
13 days agoHandshake completed641 ms
15 days agoHandshake completed679 ms
16 days agoHandshake completed665 ms
18 days agoHandshake completed670 ms
19 days agoHandshake completed679 ms
20 days agoHandshake completed622 ms
20 days agoHandshake completed670 ms
21 days agoHandshake completed661 ms
22 days agoHandshake completed679 ms

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

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