LienDeadline MCP server

Mechanics lien and notice deadlines in Claude, ChatGPT, Cursor and any MCP client

Ask your AI assistant when your preliminary notice and lien deadlines fall. Every date cites its statute, and unsupported scopes or unresolved facts return “needs review”. Guides are public; supplier discovery and calculations use your customer account.

Hosted server

Connect with one URL

Streamable HTTP. Guides are public; supplier discovery and calculations require your customer API key as a Bearer header on every exchange.

https://mcp.liendeadline.com/mcp

The install links and no-authentication connection settings below let you use public guides. Configure a dedicated customer key in your client's approved secret settings for supplier tools; never paste keys into prompts or committed files. Discovery uses no calculation allowance; completed calculations consume plan allowance.

Other clients

Claude Code

claude mcp add --transport http liendeadline https://mcp.liendeadline.com/mcp

ChatGPT

  1. Open Plugins and select +.
  2. Choose Add custom MCP server.
  3. Paste the URL above.
  4. Select No authentication.

Codex CLI

codex mcp add liendeadline --url https://mcp.liendeadline.com/mcp

Run it locally

npx -y liendeadline-mcp

Needs Node.js 22.22 or newer. The local server also serves the two customer API tools.

Example

Ask in plain language, get dates with statutes

Prompt

We supplied a Florida commercial job for a subcontractor, Aug 3 to Sep 10, 2026. No final payment, no termination. When are our notice and lien deadlines?

LienDeadline returns the Notice to Owner deadline, Sep 17, 2026, under Fla. Stat. § 713.06(2)(a), and the claim of lien deadline, Dec 9, 2026, under Fla. Stat. § 713.08(5).
Real output from the hosted connector, October 2026. An educational baseline, not legal advice.

Coverage

What it calculates today

Start with get_supplier_questions for any state or DC. The API checks the exact project type and hiring relationship. Supported private projects can return dates after the applicable facts are confirmed.

Supplier discovery and calculations (v3)
Coverage extends beyond Florida and Kansas. Start with get_supplier_questions for the exact state, project type and hiring relationship; live discovery confirms supported scopes and required facts.
Delivery-event baselines (v2)
Legacy supplier-events-v2 covers Florida and Kansas private projects. It does not define the broader v3 coverage.
Scopes and facts needing review
Unsupported scopes and unresolved facts return “needs review” with the reason. A guide or state name alone does not establish a calculated date.
Lien guides
All 50 states and DC, with statute citations.
Customer access and usage
Supplier discovery and calculations require a customer API key. Discovery uses no calculation allowance; completed calculations consume plan allowance. Guides remain public.
Invoice-based deadlines
Available with a customer API key through the local MCP server.

Tools

Five tools for guides and calculations

calculate_supplier_deadlines
Legacy v2 preliminary notice and lien filing baselines for Florida and Kansas private projects, using delivery dates and event answers.
get_supplier_questions
Start here for any state or DC. Check live coverage for the project type and hiring relationship, and get the applicable questions and sources.
calculate_supplier_deadlines_v3
Evaluates notice and lien outcomes using the rule identities from discovery and the project facts you confirm.
get_state_lien_guide
One state's lien guide: rules, statute citations, a deadline table and common questions.
list_state_lien_guides
Lists every guide, for all 50 states and DC.

Two more tools, calculate_lien_deadline and list_supported_states, calculate invoice-based deadlines with a customer API key. They run on the local server only.

Privacy and safety

Project facts and usage data

  • No filing or sending. Nothing sends notices, files liens or makes payments.
  • Deadline calculations use the project scope and confirmed event facts. Guide lookups use a state code. The hosted connector can record a goal from a fixed list for aggregate analytics.
  • Usage counted per account. Supplier discovery and calculations require your customer API key. Discovery uses no calculation allowance; completed calculations consume plan allowance. Guides remain public.

Details are in the privacy policy.