Skip to main content
Glama

Server Details

Supplier lien and notice deadlines by project scope. Public lien guides for all 50 states and DC.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
LienDeadline/liendeadline-mcp
GitHub Stars
1
Server Listing
liendeadline-mcp
ChatGPT
–
Claude
LienDeadline

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation3/5

The two deadline calculators overlap substantially: legacy calculate_supplier_deadlines and calculate_supplier_deadlines_v3 both compute supplier notice/lien deadlines, and the descriptions do not clearly state when an agent should choose one over the other. get_supplier_questions helps as a starting point, and the guide tools are distinct, but the calculator boundary remains a likely source of misselection.

Naming Consistency4/5

Names mostly follow a predictable verb_noun pattern: calculate_supplier_deadlines, get_state_lien_guide, get_supplier_questions, list_state_lien_guides. The only deviation is the _v3 suffix on the newer calculator, which is minor but breaks the otherwise clean convention.

Tool Count4/5

Five tools is a reasonable, well-scoped size for a focused lien-deadline service, covering discovery, calculation, and guide lookup without excessive surface area. The count is slightly inflated by having both a legacy and v3 calculator, but the set is still manageable.

Completeness4/5

The surface covers the core lifecycle: discover applicable questions and coverage, calculate deadlines, and consult state-specific editorial guides. Explicit out-of-scope actions like saving projects or filing liens are excluded by design, though the legacy/v3 duality adds a small completeness ambiguity rather than a true gap.

Available Tools

5 tools
calculate_supplier_deadlinesCalculate legacy Florida or Kansas supplier deadlinesAInspect

Legacy 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.

Inputs: state (required), context (required), hired_by (required), project_type (required), +8 more.

calculate_supplier_deadlines_v3Calculate supplier deadlines from confirmed project factsAInspect

Evaluates 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_notice_facts supplies actual Tennessee furnished months or New Hampshire account records. Tennessee recurring_notice_periods cover entered periods only, including paid and unknown states; known unpaid duties remain independent. New Hampshire recurring_notice_checkpoints are advisory check-ins with unresolved legal status, not legal deadlines, service, completion or scheduled reminders; they do not reset earlier gaps. Never infer intervening months or blanket completion. Stale identities return 409, unavailable reviewed sources return 503. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed.

Inputs: state (required), events (required), context (required), hired_by (required), +4 more.

get_state_lien_guideGet the lien guide for one stateA
Read-onlyIdempotent
Inspect

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.

Inputs: state (required), context (required).

get_supplier_questionsCheck supplier project coverage and questionsA
Read-onlyIdempotent
Inspect

Start 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.

Inputs: state (required), context (required), hired_by (required), project_type (required).

list_state_lien_guidesList all state guidesA
Read-onlyIdempotent
Inspect

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.

Inputs: context (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Real-time contractor license verification across 45 US states. Verifies license status, expiration, and disciplinary history directly against state licensing board portals.
      4
      67 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and procurement systems to verify contractor licenses against official state boards, search contractors by trade and location, audit workers' comp, surety bonds and OSHA safety records, and check SAM.gov federal debarment status. It returns a deterministic ALLOW/WARN/BLOCK compliance decision plus registry health metrics for US trade contractors.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.