liendeadline-mcp
LienDeadline MCP helps AI assistants look up mechanics lien and notice rules and calculate construction supplier deadlines, with statute citations.
Discover supplier deadline coverage and required questions for any US state or DC, then calculate v3 notice and lien deadlines from confirmed project facts.
Calculate legacy Florida and Kansas private-project supplier deadlines from delivery events.
Get an editorial lien guide for one state or list all 50 states and DC guides; public and no key required.
Calculate invoice-based deadlines and list supported customer API jurisdictions using a customer key.
Return review-required or no-lien-right outcomes when facts are missing or unsupported; calculations require a customer key and may consume plan allowance.
Does not send notices, file liens, or provide legal advice.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@liendeadline-mcp What's the lien deadline for a Texas invoice dated 2026-07-01?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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.
Related MCP server: sg-deadline
Quick start
Connecting to the hosted server and using public guides needs no install, account or key:
https://mcp.liendeadline.com/mcpThe 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.
Client | How to add it |
Claude (web, desktop, mobile) | Open LienDeadline in Claude's Connectors directory and connect it. |
Claude Code |
|
Cursor | |
VS Code | |
ChatGPT | Open Plugins, select + → Add custom MCP server, paste the URL above and choose No authentication. |
Codex CLI |
|
Any MCP client | Streamable 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:
claude plugin marketplace add LienDeadline/skills
claude plugin install liendeadline@liendeadlineThe 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:
claude mcp add liendeadline -- npx -y liendeadline-mcpCodex CLI:
codex mcp add liendeadline -- npx -y liendeadline-mcpCursor, Windsurf and other mcpServers clients:
{
"mcpServers": {
"liendeadline": { "command": "npx", "args": ["-y", "liendeadline-mcp"] }
}
}VS Code (.vscode/mcp.json):
{
"servers": {
"liendeadline": { "type": "stdio", "command": "npx", "args": ["-y", "liendeadline-mcp"] }
}
}What you can ask
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
What | Where | Needs |
Supplier discovery and calculations (v3) | Check any US state or DC with | Customer key. Discovery uses no calculation allowance. Completed calculations consume allowance. |
Delivery-event baselines (v2) | Florida and Kansas private projects | Customer key; completed calculations consume allowance |
Lien guides | All 50 states and DC | Nothing |
Invoice-based deadlines | 51 jurisdictions |
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
You ask your AI assistant about a job.
The assistant checks coverage and asks which facts apply to the project.
LienDeadline evaluates the confirmed facts against the discovered rules. Each calculated deadline includes its sources. Unresolved outcomes include the reason.
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
Tool | What it does | Key |
| Legacy v2 baselines for Florida and Kansas private projects | Customer |
| Whether v3 covers a state, project type and hiring relationship, with its questions, sources and rule versions | Customer |
| Deadlines from the facts gathered with | Customer |
| One state's lien guide: rules, statute citations, deadline table and FAQs | None |
| Every guide (50 states and DC) with its code, title and slug | None |
| Invoice-based deadlines (local server only) | Customer |
| Jurisdictions 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 setLIENDEADLINE_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
Website: liendeadline.com, with a setup guide for this server
Agent skill and plugins: liendeadline.com/agent-skill and LienDeadline/skills
Support: support@liendeadline.com or liendeadline.com/contact
Terms of service: liendeadline.com/terms
Privacy policy: liendeadline.com/privacy
Help center: liendeadline.com/help
Security: report issues privately as described in SECURITY.md
Contributing and development: CONTRIBUTING.md
License: MIT
Available Tools
7 toolscalculate_lien_deadlineCalculate invoice deadlines (customer API key)AInspect
Customer API tool: requires LIENDEADLINE_API_KEY, a dedicated LienDeadline customer key; without one it returns a configuration error and makes no request. Calculates the preliminary notice and lien filing deadlines for one construction invoice from its invoice or delivery date and state. Returns JSON with state, invoice_date, project_type, preliminary_notice_deadline, lien_deadline, waiver_due_date, prelim_deadline_days, lien_deadline_days, warnings such as weekend or holiday rollover, notes and a disclaimer. A date, day count or project_type the API does not return is null; missing warnings is [] and missing notes is an empty string. API denials (401 key, 403 scope, 429 rate limit) return a tool error. Successful calculations consume one API plan unit. Not legal advice.
Inputs: state (required), invoice_date (required), role, notice_date, +1 more.
calculate_supplier_deadlinesCalculate legacy Florida or Kansas supplier deadlinesAInspect
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.
Inputs: state (required), hired_by (required), project_type (required), deliveries_complete (required), +7 more.
calculate_supplier_deadlines_v3Calculate supplier deadlines from confirmed project factsAInspect
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_notice_facts supplies actual Tennessee furnished months or New Hampshire account records. Tennessee recurring_notice_periods cover entered periods only, including paid and unknown states; known unpaid duties remain independent. New Hampshire recurring_notice_checkpoints are advisory check-ins with unresolved legal status, not legal deadlines, service, completion or scheduled reminders; they do not reset earlier gaps. Never infer intervening months or blanket completion. Stale identities return 409, unavailable reviewed sources return 503. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed.
Inputs: state (required), events (required), hired_by (required), project_type (required), +3 more.
get_state_lien_guideGet the lien guide for one stateARead-onlyIdempotentInspect
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.
Inputs: state (required).
get_supplier_questionsCheck supplier project coverage and questionsARead-onlyIdempotentInspect
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.
Inputs: state (required), hired_by (required), project_type (required).
list_state_lien_guidesList all state guidesARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
list_supported_statesList customer API jurisdictions (customer API key)ARead-onlyIdempotentInspect
Customer API tool: requires LIENDEADLINE_API_KEY with the states:read scope. Returns count and the two-letter codes of the jurisdictions the customer invoice calculation accepts. It does not list editorial guides or the states with reviewed supplier baselines. Takes no parameters. Read-only.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Three tools compute lien/notice deadlines — calculate_supplier_deadlines (legacy, FL/KS only), calculate_supplier_deadlines_v3, and calculate_lien_deadline (invoice-date based) — and their boundaries are only clear after reading long descriptions, so misselection is likely. The state tools (list_state_lien_guides, list_supported_states, get_state_lien_guide) are better separated but still share near-identical naming roots. Descriptions do disambiguate once read, preventing a lower score.
All tools follow a consistent snake_case verb_noun pattern (list_*, get_*, calculate_*). The only real deviation is the versioned calculate_supplier_deadlines_v3 sitting alongside an unsuffixed legacy calculate_supplier_deadlines, which is slightly asymmetric. Otherwise readable and predictable.
Seven tools is a good scoped size for a lien-deadline domain. There is some redundancy — a legacy calculator coexisting with a v3 calculator, and a list/get pair plus a separate supported-states list. Not a sizing problem, just mild duplication.
The surface covers editorial guides (list + get), supported-jurisdiction discovery, v3 question discovery then calculation, and a simple invoice-based calculator — a coherent lifecycle for read-only deadline advice, with no writes by design. Minor gaps: no batch/multi-invoice calculation and no explicit way to enumerate states with calculated baselines versus editorial coverage, forcing agents to probe.
Maintenance
Related MCP Connectors
Computes California state court deadlines and cites the code section behind every date. No API key.
Compute deadlines in business days with public holidays (200+ countries). $0.002/call.
US federal holidays, business-day maths, invoice due dates and IRS deadlines.
Zero-signup business-day date-math API: add days, count days between dates, is-business-day.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA zero-signup business-day date arithmetic API that allows adding/subtracting working days, counting business days between two dates, and testing if a date is a business day, with custom holidays.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to call deterministic Singapore legal deadline arithmetic instead of guessing, covering Rules of Court 2021 procedural periods, Limitation Act anniversaries, contractual deemed receipt, and working-day utilities. Each tool returns a full derivation trace and requires an explicit rule id, so the rule choice and holiday data provenance stay visible in the transcript.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude Desktop and Cursor to calculate UK statutory late payment interest and fixed compensation on business-to-business invoices, including unpaid ones, and to look up the applicable Bank of England Bank Rate on a given date or across a date range. Every result is returned with its legislative sources and a not-legal-advice notice, entirely offline.MIT

Prism MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to submit leases, mortgages, insurance policies, and HOA documents and retrieve every computed deadline with its exact date, what happens if it is missed, and the clause it came from. Also supports reviewing account credits, listing contracts and upcoming deadlines, unlocking full results, and purchasing credits.MIT