Remote MCP · Endpoint

Nerf Watch MCP server

No. Nerf Watch answered an MCP handshake 54 minutes ago.

UpLast checked 54 minutes ago

Server URL

https://tokenusage.dev/mcp/nerfwatch

The last check completed an MCP handshake.

Registry name
dev.tokenusage/nerfwatch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Daily Nerf Watch scores for Claude and GPT models on one private, code-graded suite. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Nerf Watch
CheckedResultHandshake
54 minutes agoHandshake completed157 ms
3 days agoHandshake completed99 ms
12 days agoHandshake completed127 ms
13 days agoHandshake completed131 ms
14 days agoHandshake completed102 ms
15 days agoHandshake completed114 ms
16 days agoHandshake completed162 ms
17 days agoHandshake completed238 ms
18 days agoHandshake completed107 ms
19 days agoHandshake completed110 ms
22 days agoHandshake completed115 ms
25 days agoHandshake completed108 ms
27 days agoHandshake completed112 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 Nerf Watch and makes no claim about it beyond what these checks measured.