Remote MCP · Endpoint

PediBot MCP server

No. PediBot answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://pedibot.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.pedibot/pedibot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
301 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Children's health from published guidelines: doses, vaccines, growth charts, warning signs.
Listing
From the official MCP registry (active).
Recent checks of PediBot
CheckedResultHandshake
46 minutes agoHandshake completed301 ms
3 days agoHandshake completed324 ms
13 days agoHandshake completed300 ms
13 days agoHandshake completed310 ms
15 days agoHandshake completed295 ms
16 days agoHandshake completed325 ms
17 days agoHandshake completed297 ms
18 days agoHandshake completed297 ms
18 days agoHandshake completed295 ms
20 days agoHandshake completed297 ms
22 days agoHandshake completed300 ms
25 days agoHandshake completed317 ms
27 days agoHandshake completed297 ms
30 days agoHandshake completed298 ms

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

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