Remote MCP · Endpoint

CommonRig MCP server

Yes, as of 4 days ago: the server returned an HTTP error.

DownLast checked 4 days ago

Server URL

https://commonrig.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.commonrig/commonrig
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Agent operating kit for Claude Code and Codex: rules, hooks, work ledger, protocols and rig doctor.
Listing
From the official MCP registry (deprecated).
Recent checks of CommonRig
CheckedResultHandshake
4 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoHandshake completed264 ms
7 days agoHandshake completed591 ms
8 days agoHandshake completed551 ms
9 days agoHandshake completed406 ms
10 days agoHandshake completed554 ms
11 days agoHandshake completed536 ms
12 days agoHandshake completed955 ms
15 days agoHandshake completed407 ms
18 days agoHandshake completed608 ms
20 days agoHandshake completed480 ms
22 days agoHandshake completed559 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 CommonRig and makes no claim about it beyond what these checks measured.