liendeadline-mcp
Related Servers
Alternatives to liendeadline-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to submit leases, mortgages, insurance policies, and HOA documents and retrieve every computed deadline with its exact date, what happens if it is missed, and the clause it came from. Also supports reviewing account credits, listing contracts and upcoming deadlines, unlocking full results, and purchasing credits.MIT- AlicenseNot gradedqualityDmaintenanceA zero-signup business-day date arithmetic API that allows adding/subtracting working days, counting business days between two dates, and testing if a date is a business day, with custom holidays.MIT
- AlicenseAqualityBmaintenanceProvides exact calendar calculations from 1971 to 2100, including OPM and Federal Reserve holiday observance, business-day addition and counting, and invoice due dates with weekend and holiday roll rules.514 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to call deterministic Singapore legal deadline arithmetic instead of guessing, covering Rules of Court 2021 procedural periods, Limitation Act anniversaries, contractual deemed receipt, and working-day utilities. Each tool returns a full derivation trace and requires an explicit rule id, so the rule choice and holiday data provenance stay visible in the transcript.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to list U.S. federal holidays, find upcoming dates, check whether a date is a business day, add business days to a date, and count business days across a span from 2021 through 2100.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude Desktop and Cursor to calculate UK statutory late payment interest and fixed compensation on business-to-business invoices, including unpaid ones, and to look up the applicable Bank of England Bank Rate on a given date or across a date range. Every result is returned with its legislative sources and a not-legal-advice notice, entirely offline.MIT
TDQS
Scored across 7 tools
Three tools compute lien/notice deadlines — calculate_supplier_deadlines (legacy, FL/KS only), calculate_supplier_deadlines_v3, and calculate_lien_deadline (invoice-date based) — and their boundaries are only clear after reading long descriptions, so misselection is likely. The state tools (list_state_lien_guides, list_supported_states, get_state_lien_guide) are better separated but still share near-identical naming roots. Descriptions do disambiguate once read, preventing a lower score.
All tools follow a consistent snake_case verb_noun pattern (list_*, get_*, calculate_*). The only real deviation is the versioned calculate_supplier_deadlines_v3 sitting alongside an unsuffixed legacy calculate_supplier_deadlines, which is slightly asymmetric. Otherwise readable and predictable.
Seven tools is a good scoped size for a lien-deadline domain. There is some redundancy — a legacy calculator coexisting with a v3 calculator, and a list/get pair plus a separate supported-states list. Not a sizing problem, just mild duplication.
The surface covers editorial guides (list + get), supported-jurisdiction discovery, v3 question discovery then calculation, and a simple invoice-based calculator — a coherent lifecycle for read-only deadline advice, with no writes by design. Minor gaps: no batch/multi-invoice calculation and no explicit way to enumerate states with calculated baselines versus editorial coverage, forcing agents to probe.