Remote MCP · Endpoint

Plith Rigor MCP server

No. Plith Rigor answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://plith.ai/api/mcp/rigor

The last check completed an MCP handshake.

Registry name
ai.plith/rigor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Structured multi-step workflows that produce production-quality deliverables. Plan any task free.
Listing
From the official MCP registry (active).
Recent checks of Plith Rigor
CheckedResultHandshake
39 minutes agoHandshake completed148 ms
3 days agoHandshake completed230 ms
13 days agoHandshake completed197 ms
13 days agoHandshake completed412 ms
15 days agoHandshake completed212 ms
16 days agoHandshake completed291 ms
17 days agoHandshake completed195 ms
18 days agoHandshake completed310 ms
18 days agoHandshake completed189 ms
20 days agoHandshake completed267 ms
22 days agoHandshake completed669 ms
25 days agoHandshake completed262 ms

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

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