Remote MCP · Endpoint

Httpstatus MCP server

No. Httpstatus answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/httpstatus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
280 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
HTTP status code reference MCP.
Listing
From the official MCP registry (active).
Recent checks of Httpstatus
CheckedResultHandshake
1 hour agoHandshake completed280 ms
22 hours agoHandshake completed76 ms
2 days agoHandshake completed83 ms
3 days agoHandshake completed160 ms
4 days agoHandshake completed124 ms
5 days agoHandshake completed99 ms
6 days agoHandshake completed257 ms
8 days agoHandshake completed381 ms
11 days agoHandshake completed58 ms
13 days agoHandshake completed100 ms
16 days agoHandshake completed70 ms
18 days agoHandshake completed59 ms
20 days agoHandshake completed63 ms
22 days agoHandshake completed70 ms
24 days agoHandshake completed51 ms
26 days agoHandshake completed63 ms
27 days agoHandshake completed129 ms
29 days agoHandshake completed71 ms

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

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