Remote MCP · Endpoint

Chucknorris MCP server

No. Chucknorris answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/chucknorris/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/chucknorris
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
58 ms
Tools exposed
45 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Chuck Norris MCP — wraps chucknorris.io (free, no auth)
Listing
From the official MCP registry (active).
Recent checks of Chucknorris
CheckedResultHandshake
1 hour agoHandshake completed58 ms
2 days agoHandshake completed66 ms
4 days agoHandshake completed49 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed52 ms
8 days agoHandshake completed202 ms
9 days agoHandshake completed44 ms
12 days agoHandshake completed57 ms
14 days agoHandshake completed1.15 s
15 days agoFailed - the request timed out—
17 days agoHandshake completed51 ms
18 days agoHandshake completed50 ms
19 days agoHandshake completed174 ms
20 days agoHandshake completed43 ms
20 days agoHandshake completed45 ms
22 days agoHandshake completed78 ms
23 days agoHandshake completed47 ms

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

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