Skip to content

Zicron medical chronology (public) MCP server

ai.zicron.claims/medical-chronologyclaims.zicron.aistreamable-httpv1.2.0Scanned

Price, sample and request page-cited medical chronologies for law firms and LNCs. No sign-in or PHI.

5 tools: 1 do something that can't be undone, 1 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Zicron medical chronology (public) MCP server can do

The Zicron medical chronology (public) MCP server is published by claims.zicron.ai, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_chronology) and create or change data (1 tool: quote_chronology), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (request_chronology); 1 tool can send data out of your system (request_chronology).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Can't be undone 1Claude Code: ask
  • request_chronologySends Zicron a request to prepare a medical chronology for a case, on behalf of the attorney, legal nurse consultant or paralegal you are helping.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "request_chronology" says "request": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Request a medical chronology (contact request, no records)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 1Claude Code: ask
  • quote_chronologyComputes 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 ov…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Quote a medical chronology by page count
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_offerReturns 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 (plainti…No findings

    Why it is in this group

    • The name "get_offer" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Zicron's medical chronology offer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_sample_chronologyReturns 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.No findings

    Why it is in this group

    • The name "get_sample_chronology" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a sample Zicron medical chronology
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_ssdi_pilot_infoReturns 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-c…No findings

    Why it is in this group

    • The name "get_ssdi_pilot_info" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Zicron's SSDI intake-scoring pilot for firms
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:28 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://claims.zicron.ai/.well-known/oauth-protected-resource
Authorization servers
https://claims.zicron.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://claims.zicron.ai/mcp: tools/list returned 5 tools to an anonymous client, including request_chronology (irreversible), quote_chronology (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http medical-chronology https://claims.zicron.ai/mcp
claude mcp add --transport http medical-chronology https://claims.zicron.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__medical-chronology__get_offer",
      "mcp__medical-chronology__get_sample_chronology",
      "mcp__medical-chronology__get_ssdi_pilot_info"
    ],
    "ask": [
      "mcp__medical-chronology__quote_chronology",
      "mcp__medical-chronology__request_chronology"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as medical-chronology. Review it before you use it.

Capability tags behind 1 rule
  • mcp__medical-chronology__request_chronology untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.zicron.claims/medical-chronology/verify?hash=e30fbc126dc46a496b2dda159f5e085e2e981ca235642f8acbe15f2e6329156f" | jq -e '.changed == false'

Pinned hash e30fbc126dc4, from Nov 12, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.zicron.claims/medical-chronology/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.zicron.claims/medical-chronology
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.zicron.claims/medical-chronology.svg)](https://radar.anlyon.com/servers/ai.zicron.claims/medical-chronology)

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

Zicron medical chronology (public) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zicron medical chronology (public) MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Zicron medical chronology (public) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Zicron medical chronology (public) MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: request_chronology.

What tools does the Zicron medical chronology (public) MCP server have?

5 tools: 1 irreversible, 1 write, 3 read. request_chronology, quote_chronology, get_offer, get_sample_chronology and get_ssdi_pilot_info.

Does the Zicron medical chronology (public) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Zicron medical chronology (public) MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_chronology.

Has the Zicron medical chronology (public) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.