Remote MCP · Endpoint

io.github.polygraphso/litmus MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://polygraph.so/api/mcp

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

Registry name
io.github.polygraphso/litmus
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Grade MCP servers A to F with the open behavioral litmus. npm: full toolset; hosted: lookups only.
Website
https://polygraph.so/
Repository
https://github.com/polygraphso/litmus
Listing
From the official MCP registry (active).
Recent checks of io.github.polygraphso/litmus
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed137 ms
11 days agoHandshake completed336 ms
14 days agoHandshake completed144 ms
16 days agoHandshake completed170 ms
18 days agoHandshake completed128 ms
20 days agoHandshake completed149 ms
22 days agoHandshake completed364 ms
24 days agoHandshake completed1.02 s
26 days agoHandshake completed1.07 s
28 days agoHandshake completed978 ms
29 days agoHandshake completed219 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.polygraphso/litmus and makes no claim about it beyond what these checks measured.