Remote MCP · Endpoint

PlainGrade MCP server

No. PlainGrade answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://plaingrade-api.mike-tusa.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.mike-tusa.plaingrade-api/plaingrade-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
182 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
English readability scores (Flesch, Flesch-Kincaid, Fog, SMOG) and text stats. Text never stored.
Listing
From the official MCP registry (active).
Recent checks of PlainGrade
CheckedResultHandshake
1 hour agoHandshake completed182 ms
22 hours agoHandshake completed305 ms
2 days agoHandshake completed149 ms
3 days agoHandshake completed561 ms
4 days agoHandshake completed200 ms
5 days agoHandshake completed210 ms
6 days agoHandshake completed296 ms
8 days agoHandshake completed213 ms
11 days agoHandshake completed184 ms
13 days agoHandshake completed271 ms
15 days agoHandshake completed197 ms
18 days agoHandshake completed195 ms
20 days agoHandshake completed477 ms
22 days agoHandshake completed183 ms
24 days agoHandshake completed296 ms

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