Remote MCP · Endpoint

Refnusa MCP server

No. Refnusa answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://refnusa.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.refnusa/refnusa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
989 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Indonesia reference data: holidays, wages, regions, postal codes, tax, food prices, KBLI, BPS stats
Listing
From the official MCP registry (active).
Recent checks of Refnusa
CheckedResultHandshake
9 hours agoHandshake completed989 ms
4 days agoHandshake completed689 ms
14 days agoHandshake completed649 ms
15 days agoHandshake completed651 ms
15 days agoHandshake completed652 ms
17 days agoHandshake completed679 ms
18 days agoHandshake completed732 ms
19 days agoHandshake completed640 ms
20 days agoHandshake completed654 ms
21 days agoHandshake completed649 ms
23 days agoHandshake completed630 ms
26 days agoHandshake completed632 ms
28 days agoHandshake completed639 ms

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