Remote MCP · Endpoint

spokojnie – czy to normalne? MCP server

No. spokojnie – czy to normalne? answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://spokojnie-mcp.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
pl.spokojnierodzice/spokojnie
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
633 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Checked, source-linked Polish answers on child development 0–36 months. Not medical advice.
Listing
From the official MCP registry (active).
Recent checks of spokojnie – czy to normalne?
CheckedResultHandshake
20 minutes agoHandshake completed633 ms
9 days agoHandshake completed613 ms
9 days agoHandshake completed615 ms
11 days agoHandshake completed577 ms
12 days agoHandshake completed139 ms
13 days agoHandshake completed89 ms
14 days agoHandshake completed569 ms
15 days agoHandshake completed86 ms
16 days agoHandshake completed576 ms
19 days agoHandshake completed635 ms
21 days agoHandshake completed616 ms
24 days agoHandshake completed574 ms
26 days agoHandshake completed66 ms
28 days agoHandshake completed632 ms

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

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 spokojnie – czy to normalne? and makes no claim about it beyond what these checks measured.