Remote MCP · Endpoint

com.howgooditcanget/clarity-os MCP server

No. com.howgooditcanget/clarity-os answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ai.howgooditcanget.com/mcp

The last check completed an MCP handshake.

Registry name
com.howgooditcanget/clarity-os
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
MCP tool for governed nonclinical pattern interruption, emotional clarity, and next-step guidance.
Listing
From the official MCP registry (active).
Recent checks of com.howgooditcanget/clarity-os
CheckedResultHandshake
1 hour agoHandshake completed80 ms
18 hours agoHandshake completed71 ms
2 days agoHandshake completed65 ms
3 days agoHandshake completed66 ms
4 days agoHandshake completed83 ms
5 days agoHandshake completed64 ms
6 days agoHandshake completed108 ms
7 days agoHandshake completed66 ms
10 days agoHandshake completed76 ms
13 days agoHandshake completed114 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed103 ms
19 days agoHandshake completed51 ms
21 days agoHandshake completed48 ms
23 days agoHandshake completed223 ms
25 days agoHandshake completed47 ms
27 days agoHandshake completed55 ms
28 days agoHandshake completed48 ms
29 days agoHandshake completed44 ms

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

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 com.howgooditcanget/clarity-os and makes no claim about it beyond what these checks measured.