# LienDeadline (npm · liendeadline-mcp)

Statute-cited lien and notice deadlines for material suppliers; lien guides for 50 states and DC.

- Trust score: 91/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.liendeadline.com`: 80/100, [markdown](https://verifymcp.io/servers/liendeadline-liendeadline-mcp/mcp.md), [page](https://verifymcp.io/servers/liendeadline-liendeadline-mcp/mcp)
- npm · `liendeadline-mcp`: 91/100 (this document), [markdown](https://verifymcp.io/servers/liendeadline-liendeadline-mcp/liendeadline-mcp.md), [page](https://verifymcp.io/servers/liendeadline-liendeadline-mcp/liendeadline-mcp)

## Channel facts

- Registry: `npm`
- Package: `liendeadline-mcp`
- Version: `0.5.7`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to LienDeadline/liendeadline-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2970 tokens (~424/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the LienDeadline MCP server?

LienDeadline runs locally as an npm package, launched with npx -y liendeadline-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "liendeadline-liendeadline-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "liendeadline-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add liendeadline-liendeadline-mcp --command npx --arg -y --arg liendeadline-mcp
```

### Hermes

```yaml
mcp_servers:
  liendeadline-liendeadline-mcp:
    command: "npx"
    args: ["-y", "liendeadline-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "liendeadline-liendeadline-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "liendeadline-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add liendeadline-liendeadline-mcp -t stdio -c npx -a -y liendeadline-mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 91, 0)

- [functional] Package version: 0.5.4 → 0.5.7

### 2026-10-29 (score 91, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.97 → unverified
- [security] Stability: 0.97 → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 0.5.5 → 0.5.7

### 2026-10-28 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 88, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-21 (score 73, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 290 → 424
- [functional] Package version: 0.5.4 → 0.5.5

### 2026-10-20 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `calculate_supplier_deadlines` (~700 tokens)

Calculate supplier notice and lien deadlines

Calculates a construction 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.

Input parameters:

- `deliveries_complete` (boolean, required): 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.
- `first_delivery_date` (string, required): Date materials were first delivered (first furnishing), YYYY-MM-DD. Not an invoice date.
- `florida_final_payment_date` (string): Florida only: owner final-payment date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_final_payment_status=yes.
- `florida_final_payment_status` (string): 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 pr…
- `florida_termination_date` (string): 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 qualif…
- `florida_termination_status` (string): Florida only: was the original contract or notice of commencement terminated? no permits the lien baseline; yes, unknown or omitted requires qualified lien review.
- `hired_by` (string, required): Who ordered the materials from the supplier: the owner, a contractor or a subcontractor.
- `kansas_extension_status` (string): Kansas only: was a statutory lien-period extension filed and mailed? no permits the ordinary lien baseline; yes, unknown or omitted requires qualified review.
- `last_delivery_date` (string): Date of the final delivery, YYYY-MM-DD, not earlier than first_delivery_date. Required when deliveries_complete is true.
- `project_type` (string, required): Private commercial, private residential, or public (public projects always need review).
- `state` (string, required): 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.

### `get_supplier_questions` (~115 tokens)

Discover supplier project questions

Returns the current supplier-events-v3 scope support, jurisdiction-specific yes/no/unknown event questions, date policies, optional recurring_notice_intake descriptor, sources and exact rule/question identities for a material supplier. Requires a customer key; no delivery dates needed. Discovery does not consume calculation quota. A 503 means the reviewed source is unavailable. Approval of research alone does not activate a scope.

Input parameters:

- `hired_by` (string, required)
- `project_type` (string, required)
- `state` (string, required): Project jurisdiction: state or DC.

### `calculate_supplier_deadlines_v3` (~630 tokens)

Calculate from discovered supplier facts

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. 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 o…

Input parameters:

- `events` (object, required): Discovered event IDs only; missing means unknown. Date only for yes and only where the question permits it. Invoice dates are not furnishing dates.
- `hired_by` (string, required)
- `project_type` (string, required)
- `questions_identity` (object, required): Exact questions_identity from discovery.
- `recurring_notice_facts`: Only when discovery returns a matching recurring_notice_intake descriptor. Actual recurring facts only: Tennessee entered furnished months with unpaid and retainage-only answers, or New Hampshire act…
- `rules_source` (object, required): Exact rules_source from discovery for this scope.
- `state` (string, required): Project jurisdiction: state or DC.

### `calculate_lien_deadline` (~303 tokens)

Calculate invoice deadlines (customer API key)

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.

Input parameters:

- `invoice_date` (string, required): Invoice or delivery date in YYYY-MM-DD format; deadlines count from it.
- `notice_date` (string): Date a preliminary notice was actually sent, YYYY-MM-DD, if one was. Omit otherwise.
- `project_type` (string): Usually "Commercial" or "Residential". Changes the deadline in some states.
- `role` (string): Your role on the project, e.g. "supplier", "contractor", "subcontractor".
- `state` (string, required): Two-letter US state code, e.g. "TX", "CA", "DC", from the jurisdictions the customer API supports.

### `list_supported_states` (~66 tokens)

List customer API jurisdictions (customer API key)

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.

### `get_state_lien_guide` (~154 tokens)

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.

Input parameters:

- `state` (string, required): Two-letter US state or DC code, e.g. "TX"; case-insensitive.

### `list_state_lien_guides` (~76 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/liendeadline-liendeadline-mcp/liendeadline-mcp#diagnostics

## Score history

- 2026-11-05: 91
- 2026-11-04: 91
- 2026-11-03: 91
- 2026-11-02: 91
- 2026-11-01: 91
- 2026-10-31: 91
- 2026-10-30: 91
- 2026-10-29: 91
- 2026-10-28: 91
- 2026-10-27: 90
- 2026-10-26: 90
- 2026-10-25: 90
- 2026-10-24: 89
- 2026-10-23: 89
- 2026-10-22: 88
- 2026-10-21: 73
- 2026-10-20: 88
- 2026-10-19: 87
- 2026-10-18: 87
- 2026-10-17: 86
- 2026-10-16: 86
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-11: 49
- 2026-10-04: 70
- 2026-10-03: 81
- 2026-10-02: 80
- 2026-10-01: 80

## Common questions

### What is the LienDeadline MCP server?

LienDeadline is an MCP server listed in the public MCP registry as io.github.LienDeadline/liendeadline-mcp. Statute-cited lien and notice deadlines for material suppliers; lien guides for 50 states and DC. This page covers its npm package (liendeadline-mcp).

### Is the LienDeadline MCP server safe to use?

LienDeadline scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LienDeadline MCP server expose?

LienDeadline exposes 7 tools: calculate_supplier_deadlines, get_supplier_questions, calculate_supplier_deadlines_v3, calculate_lien_deadline, list_supported_states, and 2 more. Their descriptions and schemas cost roughly 2,044 tokens of context every time the server is loaded.

### Is the LienDeadline MCP server still maintained?

LienDeadline is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the LienDeadline MCP server under?

LienDeadline declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/liendeadline-mcp
- Socket report: https://socket.dev/npm/package/liendeadline-mcp
- Repository: https://github.com/LienDeadline/liendeadline-mcp
- Website: https://liendeadline.com/
- Changelog RSS feed: https://verifymcp.io/servers/liendeadline-liendeadline-mcp/liendeadline-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/liendeadline-liendeadline-mcp/liendeadline-mcp.json
- HTML version of this page: https://verifymcp.io/servers/liendeadline-liendeadline-mcp/liendeadline-mcp