Remote MCP · Endpoint

PushNotif Official MCP Server MCP server

No. PushNotif Official MCP Server answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://pushnotif.biz.id/mcp

The last check completed an MCP handshake.

Registry name
io.github.AarsyDesign/pushnotif-mcp
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
753 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Web Push (VAPID), Android (FCM), iOS (APNs), In-App Popup, Toast & Transactional Email OTP engine.
Listing
From the official MCP registry (active).
Recent checks of PushNotif Official MCP Server
CheckedResultHandshake
33 minutes agoHandshake completed753 ms
3 days agoHandshake completed759 ms
13 days agoHandshake completed784 ms
13 days agoHandshake completed770 ms
15 days agoHandshake completed772 ms
16 days agoHandshake completed750 ms
17 days agoHandshake completed762 ms
18 days agoHandshake completed311 ms
18 days agoHandshake completed2.23 s
20 days agoHandshake completed981 ms
22 days agoHandshake completed860 ms
25 days agoHandshake completed878 ms

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

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