Remote MCP · Endpoint

Dumaguete Extension MCP server

No. Dumaguete Extension answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://dumaguete-extension.aplusz.app/mcp

The last check completed an MCP handshake.

Registry name
app.aplusz.dumaguete-extension/dumaguete
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
109 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Costs, travel, visas, hospitals, weather and places for Dumaguete, Philippines.
Listing
From the official MCP registry (active).
Recent checks of Dumaguete Extension
CheckedResultHandshake
4 days agoHandshake completed109 ms
4 days agoHandshake completed163 ms
5 days agoHandshake completed71 ms
7 days agoHandshake completed49 ms
8 days agoHandshake completed236 ms
9 days agoHandshake completed57 ms
10 days agoHandshake completed71 ms
11 days agoHandshake completed99 ms
12 days agoHandshake completed366 ms
15 days agoHandshake completed56 ms
18 days agoHandshake completed88 ms
20 days agoHandshake completed87 ms
22 days agoHandshake completed195 ms
24 days agoHandshake completed147 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 Dumaguete Extension and makes no claim about it beyond what these checks measured.