Remote MCP · Endpoint

Line9 MCP server

No. Line9 answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.line9.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.line9/diagrams
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
420 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Render Mermaid with Line9 layout in your assistant.
Listing
From the official MCP registry (active).
Recent checks of Line9
CheckedResultHandshake
2 hours agoHandshake completed420 ms
1 day agoHandshake completed654 ms
3 days agoHandshake completed490 ms
3 days agoHandshake completed367 ms
4 days agoHandshake completed896 ms
5 days agoHandshake completed632 ms
7 days agoHandshake completed588 ms
10 days agoHandshake completed414 ms
12 days agoHandshake completed53 ms
15 days agoHandshake completed75 ms
17 days agoHandshake completed754 ms
19 days agoHandshake completed506 ms
21 days agoHandshake completed423 ms
23 days agoHandshake completed505 ms
25 days agoHandshake completed445 ms
26 days agoHandshake completed401 ms
28 days agoHandshake completed445 ms
29 days agoHandshake completed798 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 Line9 and makes no claim about it beyond what these checks measured.