Remote MCP · Endpoint

DraftCheck AI-writing linter MCP server

No. DraftCheck AI-writing linter answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://slopscore-nine.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.kburrus64-max/slopscore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
DraftCheck: flags AI-writing patterns in prose with fix hints. Deterministic linter, not a detector.
Listing
From the official MCP registry (active).
Recent checks of DraftCheck AI-writing linter
CheckedResultHandshake
1 hour agoHandshake completed74 ms
4 days agoHandshake completed70 ms
14 days agoHandshake completed101 ms
15 days agoHandshake completed1.92 s
15 days agoHandshake completed1.47 s
17 days agoHandshake completed241 ms
18 days agoHandshake completed1.42 s
19 days agoHandshake completed1.43 s
20 days agoHandshake completed1.45 s
21 days agoHandshake completed69 ms
23 days agoHandshake completed100 ms
25 days agoHandshake completed66 ms
28 days agoHandshake completed137 ms

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

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