LienDeadline
io.github.LienDeadline/liendeadline-mcpVersion 0.5.8Supplier lien and notice deadlines by project scope. Public lien guides for all 50 states and DC.
Status
Responds205 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:39 UTC
- Latency
- 205 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.liendeadline.com/mcpResponds205 msNo sign-in
Claude Code
claude mcp add --transport http liendeadline-mcp https://mcp.liendeadline.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: liendeadline-mcp
Remote MCP server URL: https://mcp.liendeadline.com/mcpCursor
{
"mcpServers": {
"liendeadline-mcp": {
"url": "https://mcp.liendeadline.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"liendeadline-mcp","type":"http","url":"https://mcp.liendeadline.com/mcp"}'Streamable HTTP
npm: liendeadline-mcp 0.5.8Package only
npm (npx)
claude mcp add liendeadline-mcp -- npx -y liendeadline-mcp@0.5.8Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
calculate_supplier_deadlinesLegacy 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. | No | No | No | Yes |
calculate_supplier_deadlines_v3Evaluates 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 | No | No | No | Yes |
get_state_lien_guideReturns 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. | No | Yes | Yes | Yes |
get_supplier_questionsStart 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. | No | Yes | Yes | Yes |
list_state_lien_guidesLists 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. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- Nov 7, 2026
- Updated
- Nov 7, 2026
- Categories (suggested)
- Project managementSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared