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
- AlicenseAqualityCmaintenanceProvides 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.50MIT
- 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 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
- AlicenseNot gradedqualityCmaintenanceEnables Japanese business calendar operations such as holiday checking, business day calculations, payment date calculation, fiscal year determination, and deadline tracking, all locally without external API.MIT
TDQS
Scored across 7 tools
The descriptions are unusually explicit about boundaries (editorial vs. customer API, invoice vs. delivery-event inputs), which saves the public-read trio. However, calculate_supplier_deadlines (events-v2) and calculate_supplier_deadlines_v3 (events-v3) clearly overlap, and nothing in the tool set says when to prefer one, so an agent can easily pick the stale version. list_state_lien_guides vs. list_supported_states is also a subtle list-vs-list pair that only the long descriptions disambiguate.
Names follow a consistent verb_noun snake_case pattern (get_/list_/calculate_), which is easy to scan. The deviations are minor: a version suffix on only one tool (calculate_supplier_deadlines_v3, whose unversioned sibling exists) and a slightly vague 'get_supplier_questions' next to the more specific 'get_state_lien_guide'.
Seven tools is a well-scoped surface for a reference-plus-calculation service. The only waste is the parallel v2/v3 supplier calculation pair, which arguably should have been consolidated, but overall each tool maps to a real operation.
The surface covers reference lookup (single and bulk), supported-jurisdiction discovery, invoice-based calculation, and supplier event-based calculation plus rule/question discovery, which is a coherent lifecycle for a deadline service. Gaps are modest: no event-based path for non-supplier parties (owner/GC/subcontractor), and no way to retrieve or re-check a previously computed scenario.