Remote MCP · Endpoint

Plinth MCP server

No — it is up, but it requires credentials. Plinth answered 43 minutes ago with an authentication challenge rather than a session.

Auth requiredLast checked 43 minutes ago

Server URL

https://tryplinth.dev/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
dev.tryplinth/plinth
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
72 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
App hosting your agent runs: git, deploys, staging/production, Postgres. Owner approves risky steps.
Listing
From the official MCP registry (active).
Recent checks of Plinth
CheckedResultHandshake
43 minutes agoCredentials required—
8 days agoCredentials required—
9 days agoCredentials required—
11 days agoCredentials required—
12 days agoCredentials required—
13 days agoCredentials required—
14 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoHandshake completed300 ms
26 days agoHandshake completed295 ms
28 days agoHandshake completed299 ms

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

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