[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:
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.
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:
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:
Codex CLI:
Cursor, Windsurf and other mcpServers clients:
VS Code (.vscode/mcp.json):
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
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
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