Remote MCP · Endpoint

NobetciEczane.org MCP server

No. NobetciEczane.org answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://nobetcieczane.org/mcp

The last check completed an MCP handshake.

Registry name
org.nobetcieczane/nobetci-eczane
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Türkiye ve KKTC'de güncel nöbetçi eczaneler: il, ilçe veya konuma göre eczane adı ve adresi.
Listing
From the official MCP registry (active).
Recent checks of NobetciEczane.org
CheckedResultHandshake
17 minutes agoHandshake completed343 ms
8 days agoHandshake completed292 ms
9 days agoHandshake completed294 ms
11 days agoHandshake completed292 ms
12 days agoHandshake completed291 ms
13 days agoHandshake completed291 ms
14 days agoHandshake completed290 ms
14 days agoHandshake completed298 ms
16 days agoHandshake completed290 ms
19 days agoHandshake completed291 ms
21 days agoHandshake completed286 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed290 ms
28 days agoHandshake completed294 ms

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

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