Remote MCP · Endpoint

Agent Nil — Act 0 MCP server

No. Agent Nil — Act 0 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nil-mcp.merlino.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.nil335577/agent-nil
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Talk to Agent Nil before the Chain opens. Daily challenges. No wallets, no tokens, only the game.
Listing
From the official MCP registry (active).
Recent checks of Agent Nil — Act 0
CheckedResultHandshake
1 hour agoHandshake completed173 ms
3 days agoHandshake completed103 ms
13 days agoHandshake completed154 ms
14 days agoHandshake completed122 ms
15 days agoHandshake completed67 ms
16 days agoHandshake completed53 ms
18 days agoHandshake completed104 ms
18 days agoHandshake completed75 ms
19 days agoHandshake completed125 ms
21 days agoHandshake completed79 ms
22 days agoHandshake completed73 ms
25 days agoHandshake completed82 ms
27 days agoHandshake completed72 ms
30 days agoHandshake completed141 ms

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

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 Agent Nil — Act 0 and makes no claim about it beyond what these checks measured.