Remote MCP · Endpoint

Plainrouter MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://plainrouter.com/mcp/sandbox

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

Registry name
com.plainrouter/mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Meta Ads MCP: read ad accounts and signal health; propose governed changes under Ask or Full.
Listing
From the official MCP registry (active).
Recent checks of Plainrouter
CheckedResultHandshake
1 hour 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 completed637 ms
12 days agoHandshake completed553 ms
14 days agoHandshake completed569 ms
16 days agoHandshake completed566 ms
18 days agoHandshake completed530 ms
20 days agoHandshake completed538 ms
22 days agoHandshake completed558 ms
24 days agoHandshake completed558 ms
26 days agoHandshake completed540 ms
27 days agoHandshake completed549 ms
29 days agoHandshake completed541 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.

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