Remote MCP · Endpoint

LienDeadline MCP server

No. LienDeadline answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.liendeadline.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.LienDeadline/liendeadline-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Statute-cited lien and notice deadlines for material suppliers; lien guides for 50 states and DC.
Listing
From the official MCP registry (active).
Recent checks of LienDeadline
CheckedResultHandshake
1 hour agoHandshake completed86 ms
2 days agoHandshake completed86 ms
5 days agoHandshake completed97 ms
7 days agoHandshake completed66 ms
9 days agoHandshake completed76 ms
11 days agoHandshake completed71 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed87 ms
17 days agoHandshake completed73 ms
18 days agoHandshake completed102 ms
20 days agoHandshake completed90 ms
21 days agoHandshake completed168 ms
23 days agoHandshake completed69 ms

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

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