LienDeadline
io-github-liendeadline-liendeadline-mcp declares 5 capabilities across 5 tools, with 1 critical issue.
Issues
5 of 5 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
5 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
calculate_supplier_deadlines | read |
inferred |
get_supplier_questions | read |
declared |
calculate_supplier_deadlines_v3 | read |
inferred |
get_state_lien_guide | read |
declared |
list_state_lien_guides | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-16 | 9 | tools/list on https://mcp.liendeadline.com/mcp, published in the official MCP registry as io.github.LienDeadline/liendeadline-mcp 0.5.4 |
| 2026-10-11 | 9 | tools/list on https://mcp.liendeadline.com/mcp, published in the official MCP registry as io.github.LienDeadline/liendeadline-mcp 0.5.4 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.