Remote MCP · Endpoint

io.github.Protopopov/mentalka-tests MCP server

No. io.github.Protopopov/mentalka-tests answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mentalka.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Protopopov/mentalka-tests
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
853 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free anonymous PHQ-9 depression and SAS smartphone-addiction screenings in uk, en, hr, ru, pl.
Listing
From the official MCP registry (active).
Recent checks of io.github.Protopopov/mentalka-tests
CheckedResultHandshake
5 hours agoHandshake completed853 ms
10 hours agoHandshake completed128 ms
2 days agoHandshake completed84 ms
4 days agoHandshake completed899 ms
7 days agoHandshake completed100 ms
9 days agoHandshake completed83 ms
11 days agoHandshake completed102 ms
13 days agoHandshake completed817 ms
15 days agoHandshake completed133 ms
18 days agoHandshake completed107 ms
20 days agoHandshake completed863 ms
21 days agoHandshake completed89 ms
23 days agoHandshake completed900 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 io.github.Protopopov/mentalka-tests and makes no claim about it beyond what these checks measured.