ai.zicron.claims/medical-chronology

Est-ce que ai.zicron.claims/medical-chronology est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.zicron.claims/medical-chronology » 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

• get_offer≈ 930 tokens

  Returns Zicron's done-for-you medical chronology service: what is delivered (case summary plus an all-provider timeline with a page citation on every entry), who it is for (plaintiff PI, med-mal and nursing-home firms, and legal nurse consultants), the published price per case and per page, first-case discount and refund guarantee, the wholesale offer for LNCs, 48-hour turnaround, scope limits (medical facts only; no standard-of-care, causation or damages opinions), security practices and how to start. Use this when a user asks what Zicron does, what a chronology from Zicron includes, or whether it fits their case. Read-only; no side effects. If the user already has records and a Zicron account, tell them to connect https://claims.zicron.ai/agent/mcp (OAuth) instead of requesting a chronology here.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_offer", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"for": [], "urls": {}, "error": {}, "price": {}, "scope": {}, "service": "texte", "summary": "texte", "provider": {}, "security": [], "corrections": "texte", "deliverables": [], "how_to_start": []}}

• get_sample_chronology≈ 518 tokens

  Returns links to a sample Zicron medical chronology built from a fictional case (no real patient data): a page for humans and a direct PDF link, plus the sections it contains. Use this when a user wants to see what the deliverable looks like before sending a case. Read-only; no side effects.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_sample_chronology", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "error": {}, "title": "texte", "sections": [], "provenance": "synthetic", "offer_version": "texte", "sample_pdf_url": "texte", "provenance_note": "texte", "sample_page_url": "texte", "recommended_link_for_humans": "texte"}}

• get_ssdi_pilot_info≈ 557 tokens

  Returns Zicron's 30-day SSDI intake-scoring pilot for SSDI representation and intake firms: what it does (rule-based scoring of leads against SSA's five-step evaluation with page-cited findings), price, what is included, limits, and how to request it. Use this only for law firms or intake operations handling SSDI claims. It is not for individual claimants seeking help with their own claim; Zicron does not represent claimants. Read-only; no side effects.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_ssdi_pilot_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"for": "texte", "url": "texte", "error": {}, "pilot": {}, "limits": [], "not_for": "texte", "service": "texte", "summary": "texte", "how_to_start": "texte", "offer_version": "texte"}}

• quote_chronology≈ 878 tokens

  Computes the price of a Zicron medical chronology from the approximate page count of the record set, using the published list price, and returns the breakdown (base price, pages over the included amount, first-case discount, total) and the turnaround. Deterministic; read-only; no side effects and nothing is ordered. Use this when a user asks what a chronology for N pages would cost. The result is an estimate: Zicron confirms the page count and price in writing before any work starts.

  Paramètres, retour & exemple (2)

  Paramètres

  • pages · integer · requis
    Approximate total number of pages in the medical record set.
  • first_case · boolean · optionnel
    True if this would be the requester's first case with Zicron (first case is half price).

  Exemple d'appel

  {"name": "quote_chronology", "arguments": {"pages": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"firm": true, "note": "texte", "basis": "published_list_price", "error": {}, "pages": 1, "total": 1, "currency": "USD", "subtotal": 1, "next_step": "texte", "base_price": 1, "first_case": true, "offer_version": "texte"}}

• request_chronology≈ 1698 tokens

  Sends Zicron a request to prepare a medical chronology for a case, on behalf of the attorney, legal nurse consultant or paralegal you are helping. It creates a contact request only: nothing is ordered or charged, and a person at Zicron replies by email within one business day with a firm quote and a secure upload link for the records. NEVER include medical records, patient names, dates of birth, record numbers, diagnoses or any other patient information; describe the case only by type, rough page count and deadline. Requests that look like they contain patient information are rejected. Only call this after the user has asked for it and agreed that Zicron may email them, then set confirmed_by_user=true. Use dry_run=true to validate the fields and see the quote without sending anything. Retrying with the same details (or the same idempotency_key) returns the original request instead of creating a duplicate.

  Paramètres, retour & exemple (14)

  Paramètres

  • notes · string · optionnel
    Optional short note about the case in general terms (e.g. "two hospitals and a rehab facility, need it before a mediation"). Max 500 characters. No patient names, dates of birth, diagnoses or record content.
  • phone · string · optionnel
    Requester's phone number (optional).
  • dry_run · boolean · optionnel
    If true, validate and return the estimate without sending the request.
  • deadline · string · optionnel
    When the chronology is needed back, as YYYY-MM-DD, e.g. 2026-11-15 (optional).
  • case_type · string · requis · personal_injury | medical_malpractice | nursing_home | workers_comp | other
    Type of case the chronology is for.
  • firm_name · string · optionnel
    Law firm or LNC business name (optional).
  • agent_name · string · optionnel
    Name of the AI assistant or agent making this request (e.g. "Claude", "ChatGPT"). Optional.
  • is_first_case · boolean · optionnel
    Whether this is the requester's first case with Zicron (half price). Defaults to true.
  • requester_name · string · requis
    Name of the attorney, LNC or staff member Zicron should reply to. Not the patient.
  • requester_role · string · requis · legal_nurse_consultant | lnc_firm | pi_attorney | medmal_attorney | nursing_home_attorney | paralegal | other
    The requester's role.
  • estimated_pages · integer · optionnel
    Approximate total page count of the records (optional; used for the estimate).
  • idempotency_key · string · optionnel
    Optional key; repeating a call with the same key and details returns the original request.
  • requester_email · string · requis
    Email address Zicron should reply to with the quote and secure upload link.
  • confirmed_by_user · boolean · requis
    Must be true: set only after the person you act for has asked for this and agreed Zicron may email them. Not required when dry_run is true.

  Exemple d'appel

  {"name": "request_chronology", "arguments": {"case_type": "personal_injury", "requester_name": "texte", "requester_role": "legal_nurse_consultant", "requester_email": "texte", "confirmed_by_user": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "quote": "texte", "status": "valid_not_sent", "contact": "texte", "dry_run": true, "message": "texte", "duplicate": true, "request_id": "texte", "records_policy": "texte", "what_happens_next": []}}

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://claims.zicron.ai/mcp