Remote MCP · Endpoint

io.github.kody-w/dogg-world-check MCP server

No. io.github.kody-w/dogg-world-check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rapp-agent-builder.azurewebsites.net/world/mcp

The last check completed an MCP handshake.

Registry name
io.github.kody-w/dogg-world-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
95 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verified, citable world numbers right now, each with a public tick and SHA-256 fingerprint.
Listing
From the official MCP registry (active).
Recent checks of io.github.kody-w/dogg-world-check
CheckedResultHandshake
1 hour agoHandshake completed95 ms
2 days agoHandshake completed3.74 s
5 days agoHandshake completed104 ms
7 days agoHandshake completed230 ms
9 days agoHandshake completed181 ms
11 days agoHandshake completed4.00 s
13 days agoHandshake completed112 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed102 ms
19 days agoHandshake completed88 ms
20 days agoHandshake completed100 ms
21 days agoHandshake completed99 ms
23 days agoHandshake completed110 ms

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

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 io.github.kody-w/dogg-world-check and makes no claim about it beyond what these checks measured.