Menu

Individual skill

liendeadline

Discover jurisdiction-specific supplier notice and mechanics lien deadline baselines using the LienDeadline MCP server or API. Use authenticated supplier-events-v3 discovery for the exact project scope, including supported jurisdictions beyond Florida and Kansas. Missing facts and unsupported scopes require review. Includes public statute-cited guides for all 50 states and DC.

plugins/LienDeadline/skills/skills/liendeadline/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,530
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# LienDeadline supplier deadlines

**Calculation coverage:** use `supplier-events-v3` to discover current support for the exact state, project type and hiring relationship before collecting its event facts. Supported scopes extend beyond Florida and Kansas; do not infer full coverage for a jurisdiction from one supported scope. The older `supplier-events-v2` interface remains limited to Florida and Kansas private-project baselines. Only the API decides eligibility and date availability. Report dates only when the API returns them for the submitted facts; a state guide or other reference is not a calculated result.


## Connect and check the tools

1. Installing this instruction file alone does not connect an MCP server or grant API access. For hosted MCP, configure `https://mcp.liendeadline.com/mcp` with Streamable HTTP in the client. A local LienDeadline MCP server is also supported. Use the client's approved connection and secret settings; if access has not been issued, direct the user to https://liendeadline.com/contact without asking them to paste a key.
2. Inspect the connected server's available tools and input schemas before choosing a workflow. Prefer `get_supplier_questions` and `calculate_supplier_deadlines_v3` together for jurisdiction-specific scopes. Public references use `list_state_lien_guides` and `get_state_lien_guide`. The older `calculate_supplier_deadlines` tool is usable only for the v2 coverage and event-answer schema documented below. Do not substitute the separate invoice-date tool or assume a package version proves that a tool is available.
3. If the required tools are missing, use the authorized direct HTTPS path below only when the client can securely bind the caller's credentials. Otherwise explain the missing connection or capability and provide the setup link https://liendeadline.com/mcp. Do not claim a calculated result from installation, a guide lookup or an unavailable tool.

## Access and calculation usage

1. Supplier discovery and calculations through MCP require a dedicated LienDeadline customer API key. Configure local stdio MCP with `LIENDEADLINE_API_KEY` through the client's approved secret settings. Hosted MCP and direct HTTPS supplier calls require the caller's Bearer key through an authorized credential binding. Never request or place key values in conversations, prompts or committed files; browser sessions and internal proxy/provider tokens are not substitutes. State guides remain public without a key.