Remote MCP · Endpoint

legivel MCP server

No. legivel answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://api.legivel.com/mcp

The last check completed an MCP handshake.

Registry name
com.legivel/legivel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
377 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Markdown to PDF: real formulas, repeated table headers, a contents page. 100 free documents a month.
Listing
From the official MCP registry (active).
Recent checks of legivel
CheckedResultHandshake
48 minutes agoHandshake completed377 ms
10 days agoHandshake completed388 ms
10 days agoHandshake completed385 ms
11 days agoHandshake completed392 ms
12 days agoHandshake completed376 ms
14 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—

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

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