Is the LienDeadline MCP server down?

mcp-registry/io.github.liendeadline/liendeadline-mcp · v0.5.11

Also listed as github/liendeadline/liendeadline-mcp

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 17:18 UTC · handshake 123ms

As of 2026-11-22 17:18 UTC, the LienDeadline MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.8%
checks observed
853
outages (90d)
2
tools
5

Supplier lien and notice deadlines by project scope. Public lien guides for all 50 states and DC.

Point your MCP client at this streamable-http endpoint: https://mcp.liendeadline.com/mcp

Agent-readiness: A (92/100)

A (92/100): 0 error(s), 1 warning(s) across 5 tool(s); ~3,310 tokens of tool definitions.
Scores higher than 65% of 27,661 MCP servers Glimind has audited.
Its tool list costs an agent ~3,310 tokens per session — more than 60% of servers.
93 → 92 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints100
Schemas100
Protocol100
Stability96
Token cost80
Reliability100
Client compatibility70

What to fix (3)

1 tool definition(s) exceed ~1,200 tokens each (largest: calculate_supplier_deadlines_v3, ~1,308).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~708 tokens every session. How to fix →

Tools: calculate_supplier_deadlines_v3 · saves ~708 tokens/session

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.liendeadline/liendeadline-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.liendeadline/liendeadline-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.liendeadline%2Fliendeadline-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.liendeadline%2Fliendeadline-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.liendeadline%2Fliendeadline-mcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.liendeadline%2Fliendeadline-mcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:968d1fc2a6b1828e…, first seen 2026-11-17, included at leaf 320612 of 384,710. Version history · verify what your client received.

Tools (5)

Compare: most reliable other servers · most reliable data servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the LienDeadline MCP server down right now?

As of 2026-11-22 17:18 UTC, the LienDeadline MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

How many tools does LienDeadline MCP server provide?

LienDeadline MCP server advertises 5 tools, including calculate_supplier_deadlines, calculate_supplier_deadlines_v3, get_state_lien_guide, get_supplier_questions, list_state_lien_guides.

How do I install LienDeadline MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.liendeadline.com/mcp

Is the LienDeadline MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of LienDeadline MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve