LienDeadline

io.github.LienDeadlinePublished by GitHub account LienDeadlinev0.5.8Updated Nov 7, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

LienDeadline turns construction material delivery facts into US preliminary notice and mechanics lien deadlines, with statute sources and public state lien…

What you can do
  • Check coverage and gather required facts for a supplier deadline scope in any US state or DC
  • Calculate sourced notice and lien deadlines from confirmed delivery and project facts, including review-required outcomes
  • Run legacy deadline baselines for Florida and Kansas private projects
  • Read one state's lien guide with rules, statute citations, deadline table and FAQs
  • List all published state lien guides for the 50 states and DC
When to use it
Use it when a construction material supplier needs to know preliminary notice or lien filing deadlines for a specific job, or when someone wants a state's mechanics lien rules with citations. It is a planning aid, not a filing service or legal advice.
Requirements
Remote streamable HTTP endpoint, or a local npm package needing Node.js 22.22 or newer. Public state guides need no account or key. Supplier discovery and calculations need a customer API key, sent as a bearer token by hosted callers or set in LIENDEADLINE_API_KEY for local use.
Before you install
Supplier facts (state, dates, project type, who hired the supplier, yes/no/unknown answers) are sent to the LienDeadline API to calculate. Completed calculations consume plan allowance. The hosted server logs request metadata and may send anonymous usage telemetry to PostHog. It does not send notices, file liens or make payments, and results are educational baselines to verify with counsel.

Installation

In SourceWeft

  1. Open LienDeadline in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.LienDeadline%2Fliendeadline-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "liendeadline": {
      "type": "http",
      "url": "https://mcp.liendeadline.com/mcp"
    }
  }
}

README

[LienDeadline: mechanics lien and notice deadlines for AI assistants]

[Listed in Claude's Connectors directory] [Listed in the official MCP Registry] [npm version] [Glama score] [MIT license]

[LienDeadline MCP server]

Ask your AI assistant when your preliminary notice and mechanics lien deadlines fall, and get the statute behind every date. This MCP server connects Claude, ChatGPT, Cursor, VS Code and any other MCP client to LienDeadline, the deadline engine for US construction material suppliers. There is nothing to install: add one URL.

Quick start · What you can ask · Coverage · Tools · Privacy · liendeadline.com

Why LienDeadline

Miss a preliminary notice or a lien filing deadline and a supplier can lose its lien rights on the job, and with them the leverage to get paid. The rules change with the state, the project type and who hired you. LienDeadline turns your delivery dates into those deadlines and shows its work.

  • Coverage for your exact project. Check any US state or DC, project type, and hiring relationship. For supported scopes, use the returned questions to confirm delivery dates and other facts that can affect notice and lien deadlines.
  • The statute behind every date. Each deadline cites its source, so your team and your counsel can check it.
  • Never a guessed date. Missing facts and unsupported project scopes come back as "needs review", with the reason.
  • Lien guides for all 50 states and DC. Rule summaries, deadline tables and common questions, with statute citations.
  • Safe by design. Supplier discovery and calculations require a caller customer key; completed calculations consume plan allowance. Public guides need no account or key. Nothing sends notices, files liens or makes payments.

Quick start

Connecting to the hosted server and using public guides needs no install, account or key:

https://mcp.liendeadline.com/mcp

The no-authentication connection settings below cover the transport and public guides. Supplier discovery and calculations require the caller's dedicated customer key through the client's approved credential settings. Discovery does not consume calculation allowance; completed calculations do.

ClientHow to add it
Claude (web, desktop, mobile)Open LienDeadline in Claude's Connectors directory and connect it.
Claude Codeclaude mcp add --transport http liendeadline https://mcp.liendeadline.com/mcp
Cursor[Install in Cursor]
VS Code[Install in VS Code]
ChatGPTOpen Plugins, select + → Add custom MCP server, paste the URL above and choose No authentication.
Codex CLIcodex mcp add liendeadline --url https://mcp.liendeadline.com/mcp
Any MCP clientStreamable HTTP at the URL above. Public guides need no authentication; supplier tools need a customer key.

Want your agent to ask the right questions too? The LienDeadline agent skill (GitHub) teaches it which facts to collect. The Claude Code plugin adds the skill and this server in one step:

bash
claude plugin marketplace add LienDeadline/skillsclaude plugin install liendeadline@liendeadline
Run it locally instead (npm, stdio)

The local server needs Node.js 22.22 or newer and serves every tool, including the two customer API tools. It ships npm-shrinkwrap.json, so npx installs the exact dependency versions each release was tested with.

Claude Desktop: download liendeadline-mcp-<version>.mcpb from the latest release and open it.

Claude Code:

bash
claude mcp add liendeadline -- npx -y liendeadline-mcp

Codex CLI:

bash
codex mcp add liendeadline -- npx -y liendeadline-mcp

Cursor, Windsurf and other mcpServers clients:

json
{  "mcpServers": {    "liendeadline": { "command": "npx", "args": ["-y", "liendeadline-mcp"] }  }}

VS Code (.vscode/mcp.json):

json
{  "servers": {    "liendeadline": { "type": "stdio", "command": "npx", "args": ["-y", "liendeadline-mcp"] }  }}

What you can ask

[A Florida supplier asks for its 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)]

Try asking:

  • "What facts do you need to check supplier deadlines for a Maryland commercial project where the owner hired us directly?"
  • "We delivered to a Florida commercial job for a subcontractor from Aug 3 to Sep 10, 2026. No final payment, no termination. When are our notice and lien deadlines?"
  • "Same job, but I don't know whether the owner made final payment. What can you tell me?"
  • "Walk me through Texas mechanics lien rules for a material supplier and cite the statutes."
  • "Which states do you have lien guides for? Show me Georgia's."

Coverage

WhatWhereNeeds
Supplier discovery and calculations (v3)Check any US state or DC with get_supplier_questions. Dates depend on the exact scope and confirmed facts.Customer key. Discovery uses no calculation allowance. Completed calculations consume allowance.
Delivery-event baselines (v2)Florida and Kansas private projectsCustomer key; completed calculations consume allowance
Lien guidesAll 50 states and DCNothing
Invoice-based deadlines51 jurisdictionsA customer API key

The website calculator and the v3 tools use the API's current reviewed rules. Start with discovery for the exact project. Supported private scopes can produce dates after the relevant facts are confirmed. Public projects and unsupported scopes require qualified review. Unresolved facts can also leave individual deadlines under review. An unavailable reviewed source returns an error.

How it works

  1. You ask your AI assistant about a job.
  2. The assistant checks coverage and asks which facts apply to the project.
  3. LienDeadline evaluates the confirmed facts against the discovered rules. Each calculated deadline includes its sources. Unresolved outcomes include the reason.
  4. Before showing a supplier deadline, the server checks that the result echoes exactly the facts you sent. A mismatch is reported as an error, never as a date.

Tools

ToolWhat it doesKey
calculate_supplier_deadlinesLegacy v2 baselines for Florida and Kansas private projectsCustomer
get_supplier_questionsWhether v3 covers a state, project type and hiring relationship, with its questions, sources and rule versionsCustomer
calculate_supplier_deadlines_v3Deadlines from the facts gathered with get_supplier_questionsCustomer
get_state_lien_guideOne state's lien guide: rules, statute citations, deadline table and FAQsNone
list_state_lien_guidesEvery guide (50 states and DC) with its code, title and slugNone
calculate_lien_deadlineInvoice-based deadlines (local server only)Customer
list_supported_statesJurisdictions the invoice calculation accepts (local server only)Customer

Inputs, outputs and statuses are in the tool reference.

Privacy and safety

  • Account usage. Supplier discovery and calculations require a customer key. Discovery uses no calculation allowance; completed calculations consume plan allowance. Hosted callers send their own Authorization: Bearer <key> on each request; local callers set LIENDEADLINE_API_KEY. The hosted server never uses a service-wide key. State guides remain public.
  • What's sent. The facts you give (state, dates, project type, who hired you and your yes, no or unknown answers) go to the LienDeadline API to calculate. Guide lookups send only a state code.
  • Hosted server. Its logs record the method, status and response time of each request, never your inputs. Google Cloud's own request log also records the URL, client IP address and user agent. The server may count usage anonymously in PostHog, including tool name, success, duration, client family and a goal from a fixed list. The telemetry excludes tool inputs, results and IP addresses.
  • Local server. It has no telemetry of its own.

Details: LienDeadline privacy policy.

Not legal advice

Results are educational baselines calculated from published state rules. Statutes change and every project is different, so verify critical deadlines with counsel before relying on them. LienDeadline is not a law firm and does not file anything on your behalf.

Links

Source: README.md at commit db0508e

Tools

5

calculate_supplier_deadlines

Calculate legacy Florida or Kansas supplier deadlines

Legacy calculator for Florida and Kansas private projects. Calculates a material supplier's preliminary notice and lien filing deadlines from delivery events (contract supplier-events-v2), for questions that need deadline dates. Available baselines cover Florida and Kansas private projects; other states and public projects return review_required, which is a valid result, not an error. How the parameters depend on each other: last_delivery_date is required when deliveries_complete is true. Florida (FL) takes florida_final_payment_status and florida_termination_status; Kansas (KS) takes kansas_extension_status; these are rejected for other states. Each takes yes, no or unknown: an omitted or unknown answer keeps the affected deadline under review, and a blanket review flag is not accepted. The Florida final-payment answer holds the notice for suppliers not hired by the owner. A Florida event date is accepted only with the matching yes answer. Delivery dates are furnishing dates, not invoice dates. Returns JSON with an overall status (calculated or review_required), preliminary_notice and lien_filing (each with its own status: calculated, not_required, review_required or awaiting_final_delivery, plus deadline, days_from_now, description and statute source_url), critical_warnings, statute_citations, an exact echo of the submitted inputs and a disclaimer. Invalid or contradictory facts return an error naming the field before any API call. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed. Not legal advice.

Parametersstaterequiredcontextrequiredhired_byrequiredproject_typerequiredlast_delivery_datedeliveries_completerequiredfirst_delivery_daterequiredkansas_extension_statusflorida_termination_dateflorida_final_payment_dateflorida_termination_statusflorida_final_payment_status

get_supplier_questions

Check supplier project coverage and questions

Start here for a material supplier deadline. Check live supplier-events-v3 coverage for any US state or DC, project type, and hiring relationship. Returns supported, review_required, or no_lien_right with a reason, applicable event questions, date policies, sources, and exact rule and question identities. It may also return recurring_notice_intake and short-form guidance. Confirm ordinary answers against the project facts. Requires a customer key. Discovery needs no delivery dates and uses no calculation allowance. A 503 means the reviewed source is unavailable.

Parametersstaterequiredcontextrequiredhired_byrequiredproject_typerequired

calculate_supplier_deadlines_v3

Calculate supplier deadlines from confirmed project facts

Evaluates confirmed supplier-events-v3 facts against the rule and question identities from v3 discovery. Returns separate sourced notice and lien outcomes, including qualified review when relevant facts are unresolved, and an exact nested input echo. When RI discovery asks ri_mailed_within_200_days after ri_mailed=yes, confirm whether mailing occurred within 200 days of first delivery. No, Unknown or omitted confirmation requires review; recording alone does not establish a 40-day target. Only calculated outcomes contain calculated deadline dates. Report every candidate_deadlines entry with its ID, date and sources under the API explanation. For NH review fallbacks, first_furnishing is a conservative checkpoint and final_furnishing is informational pending contract grouping and qualifying completion; passing the first checkpoint does not itself establish expiry. A calculated contract_completion outcome uses only the returned deadline, without substituting the first checkpoint or recomputing a date. Review candidates do not establish filing deadlines, completion or scheduled reminders. An optional preliminary_notice.notice_duties collection contains independently required named notices, each with its own calculated date, explanation and sources; the legacy preliminary date is only their earliest summary. Report every validated duty without inferring duties from candidates or treating one notice as satisfying all duties. A separate optional preliminary_notice.planned_notice_targets collection contains qualified intent planning targets with their target dates, assumed filing dates, full ten- or thirty-day intervals, explanations and sources. Planning targets do not establish statutory expirations, actual filing, notice completion or scheduled notifications. An optional verified action_by is a Conservative action date planning target under qualified review; the statutory deadline and countdown remain unresolved, with explanation, sources and warnings. Optional recurring

Parametersstaterequiredeventsrequiredcontextrequiredhired_byrequiredproject_typerequiredrules_sourcerequiredquestions_identityrequiredrecurring_notice_facts

get_state_lien_guide

Get the lien guide for one state

Returns LienDeadline's editorial mechanics lien and preliminary notice guide for one state or DC: rules (rule summary with statute citations), deadline_rows (deadline table), faqs (common questions) and source_url (the guide's web page), roughly 4 KB of JSON. For questions about how a state's lien or notice rules work, why a deadline falls where it does, or which statute applies. An unknown state code returns an error. The guide is an editorial reference, not a calculation: its day counts are summaries, not computed deadlines. Public and read-only; no key needed.

Parametersstaterequiredcontextrequired

list_state_lien_guides

List all state guides

Lists every published state lien guide in one response, without pagination: count plus state_code, title and slug for all 50 states and DC, in alphabetical order by state name. It lists editorial guides only and does not indicate which states have calculated deadlines. Takes no parameters. Public and read-only; no key needed.

Parameterscontextrequired

Version history

9
  1. v0.5.8LatestNov 7, 2026
  2. v0.5.7Oct 29, 2026
  3. v0.5.5Oct 21, 2026
  4. v0.5.4Oct 7, 2026
  5. v0.5.3Oct 7, 2026
  6. v0.5.0Oct 6, 2026
  7. v0.4.1Oct 4, 2026
  8. v0.4.0Oct 4, 2026
  9. v0.3.1Sep 30, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts