io.github.LienDeadline/liendeadline-mcp

Est-ce que io.github.LienDeadline/liendeadline-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.LienDeadline/liendeadline-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• calculate_supplier_deadlines≈ 1176 tokens

  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. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed. Not legal advice.

  Paramètres, retour & exemple (11)

  Paramètres

  • state · string · requis
    Two-letter code of the state where the project is located, e.g. "FL", "KS", "TX"; any state or DC is accepted. Decides which event questions apply.
  • hired_by · string · requis · owner | contractor | subcontractor
    Who ordered the materials from the supplier: the owner, a contractor or a subcontractor.
  • project_type · string · requis · commercial | residential | public
    Private commercial, private residential, or public (public projects always need review).
  • last_delivery_date · string · optionnel
    Date of the final delivery, YYYY-MM-DD, not earlier than first_delivery_date. Required when deliveries_complete is true.
  • deliveries_complete · boolean · requis
    true when the final delivery has happened (then last_delivery_date is required); false while deliveries are ongoing, which returns awaiting_final_delivery for the lien date.
  • first_delivery_date · string · requis
    Date materials were first delivered (first furnishing), YYYY-MM-DD. Not an invoice date.
  • kansas_extension_status · string · optionnel · yes | no | unknown
    Kansas only: was a statutory lien-period extension filed and mailed? no permits the ordinary lien baseline; yes, unknown or omitted requires qualified review.
  • florida_termination_date · string · optionnel
    Florida only: contract or notice-of-commencement termination date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_termination_status=yes; a lien date still requires qualified review.
  • florida_final_payment_date · string · optionnel
    Florida only: owner final-payment date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_final_payment_status=yes.
  • florida_termination_status · string · optionnel · yes | no | unknown
    Florida only: was the original contract or notice of commencement terminated? no permits the lien baseline; yes, unknown or omitted requires qualified lien review.
  • florida_final_payment_status · string · optionnel · yes | no | unknown
    Florida only: did the owner make final payment to the contractor? unknown when not verified. For suppliers not hired by the owner, unknown, omitted, or yes without florida_final_payment_date makes preliminary notice review_required.

  Exemple d'appel

  {"name": "calculate_supplier_deadlines", "arguments": {"state": "texte", "hired_by": "owner", "project_type": "commercial", "deliveries_complete": true, "first_delivery_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_supplier_deadlines_v3≈ 1671 tokens

  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. When RI discovery asks ri_mailed_within_200_days after ri_mailed=yes, confirm whether mailing occurred within 200 days of first delivery. No, Unknown or omitted confirmation requires review; recording alone does not establish a 40-day target. Only calculated outcomes contain calculated deadline dates. Report every candidate_deadlines entry with its ID, date and sources under the API explanation. For NH review fallbacks, first_furnishing is a conservative checkpoint and final_furnishing is informational pending contract grouping and qualifying completion; passing the first checkpoint does not itself establish expiry. A calculated contract_completion outcome uses only the returned deadline, without substituting the first checkpoint or recomputing a date. Review candidates do not establish filing deadlines, completion or scheduled reminders. An optional preliminary_notice.notice_duties collection contains independently required named notices, each with its own calculated date, explanation and sources; the legacy preliminary date is only their earliest summary. Report every validated duty without inferring duties from candidates or treating one notice as satisfying all duties. A separate optional preliminary_notice.planned_notice_targets collection contains qualified intent planning targets with their target dates, assumed filing dates, full ten- or thirty-day intervals, explanations and sources. Planning targets do not establish statutory expirations, actual filing, notice completion or scheduled notifications. An optional verified action_by is a Conservative action date planning target under qualified review; the statutory deadline and countdown remain unresolved, with explanation, sources and warnings. Optional recurring_notice_facts supplies actual Tennessee furnished months or New Hampshire account records. Tennessee recurring_notice_periods cover entered periods only, including paid and unknown states; known unpaid duties remain independent. New Hampshire recurring_notice_checkpoints are advisory check-ins with unresolved legal status, not legal deadlines, service, completion or scheduled reminders; they do not reset earlier gaps. Never infer intervening months or blanket completion. Stale identities return 409, unavailable reviewed sources return 503. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed.

  Paramètres, retour & exemple (7)

  Paramètres

  • state · string · requis
    Project jurisdiction: state or DC.
  • events · object · requis
    Discovered event IDs only; missing means unknown. Date only for yes and only where the question permits it. Invoice dates are not furnishing dates.
  • hired_by · string · requis · owner | contractor | subcontractor
  • project_type · string · requis · commercial | residential | public
  • rules_source · object · requis
    Exact rules_source from discovery for this scope.
  • questions_identity · object · requis
    Exact questions_identity from discovery.
  • recurring_notice_facts · ? · optionnel
    Only when discovery returns a matching recurring_notice_intake descriptor. Actual recurring facts only: Tennessee entered furnished months with unpaid and retainage-only answers, or New Hampshire actual written accounts with coverage and supplied dates. Omission retains legacy behavior; unknown answers require review. Do not infer intervening months or actual notice from a plan. NH actual owner notice belongs in the discovered nh_owner_notice_given event.

  Exemple d'appel

  {"name": "calculate_supplier_deadlines_v3", "arguments": {"state": "texte", "events": {}, "hired_by": "owner", "project_type": "commercial", "rules_source": {}, "questions_identity": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_state_lien_guide≈ 273 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • state · string · requis
    Two-letter US state or DC code, e.g. "TX"; case-insensitive.

  Exemple d'appel

  {"name": "get_state_lien_guide", "arguments": {"state": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_supplier_questions≈ 282 tokens

  Returns the current supplier-events-v3 scope support, jurisdiction-specific yes/no/unknown event questions, date policies, optional recurring_notice_intake descriptor, sources and exact rule/question identities for a material supplier. Requires a customer key; no delivery dates needed. Discovery does not consume calculation quota. A 503 means the reviewed source is unavailable. Approval of research alone does not activate a scope.

  Paramètres, retour & exemple (3)

  Paramètres

  • state · string · requis
    Project jurisdiction: state or DC.
  • hired_by · string · requis · owner | contractor | subcontractor
  • project_type · string · requis · commercial | residential | public

  Exemple d'appel

  {"name": "get_supplier_questions", "arguments": {"state": "texte", "hired_by": "owner", "project_type": "commercial"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_state_lien_guides≈ 167 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_state_lien_guides", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.liendeadline.com/mcp