Remote MCP · Endpoint

Crivum MCP server

No. Crivum answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://crivum.org/mcp

The last check completed an MCP handshake.

Registry name
org.crivum/crivum
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
256 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Score academic and professional writing against published criteria with three reference models.
Listing
From the official MCP registry (active).
Recent checks of Crivum
CheckedResultHandshake
1 hour agoHandshake completed256 ms
2 days agoHandshake completed224 ms
4 days agoHandshake completed272 ms
5 days agoHandshake completed383 ms
7 days agoHandshake completed182 ms
8 days agoHandshake completed181 ms
9 days agoHandshake completed183 ms
12 days agoHandshake completed174 ms
13 days agoHandshake completed190 ms
15 days agoHandshake completed169 ms
17 days agoHandshake completed171 ms
18 days agoHandshake completed178 ms
19 days agoHandshake completed172 ms
20 days agoHandshake completed190 ms
21 days agoHandshake completed171 ms
21 days agoHandshake completed198 ms
23 days agoHandshake completed189 ms

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

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