liendeadline-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIENDEADLINE_API_KEY | No | Optional customer API key. Only calculate_lien_deadline and list_supported_states need a key; the public tools work without a key. Set in the MCP process environment, e.g. in the server's env block. | |
| LIENDEADLINE_API_URL | No | Accepts a bare HTTP(S) origin for the public tools; customer tools reject every other origin, including staging, alternate ports and insecure HTTP. URL credentials, paths, queries and fragments are rejected. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_supplier_deadlinesA | 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. Public, stateless and read-only: no key needed, nothing is stored, and no notice is sent or lien filed. Not legal advice. |
| get_supplier_questionsB | 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. Approval of research alone does not activate a scope. |
| calculate_supplier_deadlines_v3A | 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 return 409, unavailable reviewed sources return 503. Public, stateless and read-only; no key, stored records, sent notices or filed liens. |
| calculate_lien_deadlineA | 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. Read-only. Not legal advice. |
| list_supported_statesA | 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_guideA | 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. |
| list_state_lien_guidesA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The three deadline-calculation tools (calculate_supplier_deadlines, calculate_supplier_deadlines_v3, calculate_lien_deadline) share a core purpose, and the v2/v3 pair in particular is hard for an agent to choose between since the version suffix implies supersession rather than a distinct input model. To their credit, the descriptions carefully delineate inputs (delivery events vs. project facts vs. invoice date) and key requirements, and the guide/list tools are cleanly separated.
Nearly every tool follows a clean verb_noun snake_case pattern (calculate_*, get_*, list_*), which is highly predictable. The only deviation is the '_v3' version suffix on calculate_supplier_deadlines_v3, which breaks the otherwise uniform convention.
Seven tools is well-scoped for a lien/deadline domain: three calculation entry points, two list tools, and two retrieval tools, each with a distinct role. No obvious filler or bloat.
The surface covers the lifecycle reasonably well: deadline calculations across two data models and an invoice-based customer API, plus editorial guides, state lists, and question discovery. The main gap is that coverage is limited to FL/KS private projects and the invoice API, with public projects and other states returning review_required, but that is an explicit design boundary rather than a dead end.