LienDeadline

Supplier notice and mechanics lien deadline baselines for Florida and Kansas private projects, plus statute-cited guides for all 50 states and DC.

Other supplier calculations require review.

MCP connector

Server URL: https://mcp.liendeadline.com/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: For jurisdiction-specific questions, first use for the exact state, project type and hiring relationship. It returns live scope support, event questions and rule identities. Ask those questions without guessing; use with those identities and nested event answers. Review-required and no-lien-right outcomes remain distinct. 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. When preliminary_notice.notice_duties is present, report every named notice with its own calculated date, explanation and sources; the legacy preliminary_notice.deadline is only the earliest summary. Preserve the validated collection and never infer independent notices from candidates or treat one notice as satisfying all duties. When preliminary_notice.planned_notice_targets is present, report every Intent planning target with its target date, assumed filing date, full ten- or thirty-day interval, explanation and sources. Earlier actual filing requires the full interval before that filing. Preserve these qualified plans separately from confirmed notices: they do not establish a statutory expiration, actual filing, sent notice, completion or scheduled notification. Submit optional recurring_notice_facts only when the exact discovery returns a matching recurring_notice_intake descriptor. Its absence means no recurring intake is available for that scope; never infer it from the state alone. Optional recurring_notice_facts records actual Tennessee furnished months or New Hampshire written accounts. Report Tennessee recurring_notice_periods only for entered months, including paid and unknown periods, with entered_periods_only coverage. Do not infer intervening months or complete later occurrences from an earlier completion. Report New Hampshire recurring_notice_checkpoints as advisory account check-ins with unresolved legal status and their actual anchor and coverage. These checkpoints do not establish a legal deadline, service, completion, reminder or a blanket cadence reset; earlier gaps remain unresolved. Report every returned candidate_deadlines entry with its ID, date and sources, preserving the API explanation and qualified review. For New Hampshire review fallbacks, identify first_furnishing as a conservative checkpoint and final_furnishing as informational pending contract grouping and qualifying completion. Passing the first checkpoint does not itself establish expiry. A calculated contract_completion outcome uses only the API-returned deadline; do not substitute the first-furnishing checkpoint or recompute a date. Review candidates do not establish calculated filing deadlines, notice completion or scheduled reminders. If a verified review_required outcome returns action_by, label it Conservative action date, preserve its explanation, sources and critical warnings, and retain qualified review: it is a planning target while the statutory deadline remains unresolved, with no statutory countdown. Never infer an action date from candidates, guides or memory. A 409 requires fresh discovery and confirmation; a 503 means this interface is unavailable and is not permission to infer new coverage. The existing v2 calculator remains available for its stated scope. US mechanics lien and preliminary notice deadlines for construction material suppliers. requires a customer key and counts against the plan: give it the project state, first delivery date, final delivery date when deliveries are complete, project type and who hired the supplier. Answer Florida final-payment and termination or Kansas extension questions explicitly as yes, no or unknown; missing and unknown facts need review. The Florida final-payment question applies to suppliers not hired by the owner: unknown, omitted, or yes without a date makes preliminary notice review_required. Available date baselines cover Florida and Kansas private projects; every other case returns review_required, which is an answer, not a failure. Ask for missing facts rather than guessing, and never substitute an invoice date for delivery dates. and return editorial guides with statute citations for all 50 states plus DC: use to explain the rules behind a date and to find valid state codes. Guide day counts are editorial summaries; take statutory dates only from verified calculated outcomes of or , and treat unresolved outcomes as requiring qualified review. Research approval for a jurisdiction does not enable its calculations; take dates only from a successful calculation response for the submitted facts. Results are calculated baselines, not legal advice.

Tools

Reads data3

Changes data2

Skills

1 in the Claude listing

MCP connector

Server URL

https://mcp.liendeadline.com/mcp

None

Protocol

MCP 2025-11-25

Instructions

For jurisdiction-specific questions, first use for the exact state, project type and hiring relationship. It returns live scope support, event questions and rule identities. Ask those questions without guessing; use with those identities and nested event answers. Review-required and no-lien-right outcomes remain distinct. 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. When preliminary_notice.notice_duties is present, report every named notice with its own calculated date, explanation and sources; the legacy preliminary_notice.deadline is only the earliest summary. Preserve the validated collection and never infer independent notices from candidates or treat one notice as satisfying all duties. When preliminary_notice.planned_notice_targets is present, report every Intent planning target with its target date, assumed filing date, full ten- or thirty-day interval, explanation and sources. Earlier actual filing requires the full interval before that filing. Preserve these qualified plans separately from confirmed notices: they do not establish a statutory expiration, actual filing, sent notice, completion or scheduled notification. Submit optional recurring_notice_facts only when the exact discovery returns a matching recurring_notice_intake descriptor. Its absence means no recurring intake is available for that scope; never infer it from the state alone. Optional recurring_notice_facts records actual Tennessee furnished months or New Hampshire written accounts. Report Tennessee recurring_notice_periods only for entered months, including paid and unknown periods, with entered_periods_only coverage. Do not infer intervening months or complete later occurrences from an earlier completion. Report New Hampshire recurring_notice_checkpoints as advisory account check-ins with unresolved legal status and their actual anchor and coverage. These checkpoints do not establish a legal deadline, service, completion, reminder or a blanket cadence reset; earlier gaps remain unresolved. Report every returned candidate_deadlines entry with its ID, date and sources, preserving the API explanation and qualified review. For New Hampshire review fallbacks, identify first_furnishing as a conservative checkpoint and final_furnishing as informational pending contract grouping and qualifying completion. Passing the first checkpoint does not itself establish expiry. A calculated contract_completion outcome uses only the API-returned deadline; do not substitute the first-furnishing checkpoint or recompute a date. Review candidates do not establish calculated filing deadlines, notice completion or scheduled reminders. If a verified review_required outcome returns action_by, label it Conservative action date, preserve its explanation, sources and critical warnings, and retain qualified review: it is a planning target while the statutory deadline remains unresolved, with no statutory countdown. Never infer an action date from candidates, guides or memory. A 409 requires fresh discovery and confirmation; a 503 means this interface is unavailable and is not permission to infer new coverage. The existing v2 calculator remains available for its stated scope. US mechanics lien and preliminary notice deadlines for construction material suppliers. requires a customer key and counts against the plan: give it the project state, first delivery date, final delivery date when deliveries are complete, project type and who hired the supplier. Answer Florida final-payment and termination or Kansas extension questions explicitly as yes, no or unknown; missing and unknown facts need review. The Florida final-payment question applies to suppliers not hired by the owner: unknown, omitted, or yes without a date makes preliminary notice review_required. Available date baselines cover Florida and Kansas private projects; every other case returns review_required, which is an answer, not a failure. Ask for missing facts rather than guessing, and never substitute an invoice date for delivery dates. and return editorial guides with statute citations for all 50 states plus DC: use to explain the rules behind a date and to find valid state codes. Guide day counts are editorial summaries; take statutory dates only from verified calculated outcomes of or , and treat unresolved outcomes as requiring qualified review. Research approval for a jurisdiction does not enable its calculations; take dates only from a successful calculation response for the submitted facts. Results are calculated baselines, not legal advice.