Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
LienDeadline is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
21
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
US mechanics lien and preliminary notice deadlines for construction suppliers, with statute sources.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user liendeadline-mcp '--' npx -y liendeadline-mcp
# 2 — ask your agent for something these tools do
# calculate_supplier_deadlines, get_supplier_questions, calculate_supplier_deadlines_v3 and 4 more
LienDeadline costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts LienDeadline as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user liendeadline-mcp '--' npx -y liendeadline-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take LIENDEADLINE_API_KEY (Optional dedicated customer key for the customer invoice tools; the supplier calculation and state guides need no key.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Calculates a construction material supplier's preliminary notice and lien filing deadlines
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter code of the state where the project is located, e.g. "FL", "KS", "TX"; any state or DC is accepted. Decides which event questions apply. |
| first_delivery_date | string | yes | Date materials were first delivered (first furnishing), YYYY-MM-DD. Not an invoice date. |
| last_delivery_date | string | no | Date of the final delivery, YYYY-MM-DD, not earlier than first_delivery_date. Required when deliveries_complete is true. |
| project_type | string | yes | Private commercial, private residential, or public (public projects always need review). |
| hired_by | string | yes | Who ordered the materials from the supplier: the owner, a contractor or a subcontractor. |
| deliveries_complete | boolean | yes | true when the final delivery has happened (then last_delivery_date is required); false while deliveries are ongoing, which returns awaiting_final_delivery for the lien date. |
| florida_final_payment_status | string | no | Florida only: did the owner make final payment to the contractor? unknown when not verified. For suppliers not hired by the owner, unknown, omitted, or yes without florida_final_payment_date makes pre |
| florida_termination_status | string | no | Florida only: was the original contract or notice of commencement terminated? no permits the lien baseline; yes, unknown or omitted requires qualified lien review. |
| florida_final_payment_date | string | no | Florida only: owner final-payment date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_final_payment_status=yes. |
| florida_termination_date | string | no | Florida only: contract or notice-of-commencement termination date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_termination_status=yes; a lien date still requires qualifi |
| kansas_extension_status | string | no | Kansas only: was a statutory lien-period extension filed and mailed? no permits the ordinary lien baseline; yes, unknown or omitted requires qualified review. |
Returns the current supplier-events-v3 scope support, jurisdiction-specific yes/no/unknown event questions, date policies, sources and exact rule/question identities for a material supplier. Public and read-only; no key or delivery dates needed. A 503 means the reviewed source is unavailable.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Project jurisdiction: state or DC. |
| project_type | string | yes | — |
| hired_by | string | yes | — |
Evaluates supplier-events-v3 project facts against the exact discovered rule and question identities. Returns independent notice and lien outcomes with sources and an exact nested input echo. Only calculated outcomes contain deadline dates; review candidates remain unresolved. Stale identities…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rules_source | object | yes | Exact rules_source from discovery for this scope. |
| questions_identity | object | yes | Exact questions_identity from discovery. |
| events | object | yes | Discovered event IDs only; missing means unknown. Date only for yes and only where the question permits it. Invoice dates are not furnishing dates. |
Customer API tool: requires LIENDEADLINE_API_KEY, a dedicated LienDeadline customer key;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state code, e.g. "TX", "CA", "DC", from the jurisdictions the customer API supports. |
| invoice_date | string | yes | Invoice or delivery date in YYYY-MM-DD format; deadlines count from it. |
| project_type | string | no | Usually "Commercial" or "Residential". Changes the deadline in some states. |
| notice_date | string | no | Date a preliminary notice was actually sent, YYYY-MM-DD, if one was. Omit otherwise. |
| role | string | no | Your role on the project, e.g. "supplier", "contractor", "subcontractor". |
Customer API tool: requires LIENDEADLINE_API_KEY with the states:read scope. Returns count and
No parameter schema on file.
Returns LienDeadline's editorial mechanics lien and preliminary notice guide for one state or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter US state or DC code, e.g. "TX"; case-insensitive. |
Lists every published state lien guide in one response, without pagination: count plus
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LienDeadline or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.5.4 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest6aa8dfd23a78a8280468536627909fbcdcad37571c8ed3c5a0936f1980b567f0
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
2 of the 7 recovered tools are registered only when options.includeCustomerTools holds (dist/server.js:182) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 5.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
5 tools are registered unconditionally · 2 more only when options.includeCustomerTools holds (dist/server.js:182) — typically when a key or option is configured. All 7 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| calculate_supplier_deadlines | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_supplier_questions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_supplier_deadlines_v3 | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| calculate_lien_deadline conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_supported_states conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_state_lien_guide | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_state_lien_guides | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6aa8dfd23a78a828
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.4. Pin a release below and the command asks for exactly that one.
0.5.4
7 Oct 2026
latestNo release note was published with this version.
0.4.2
6 Oct 2026
No release note was published with this version.
0.4.1
4 Oct 2026
No release note was published with this version.
0.3.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LienDeadline can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.