# Zicron medical chronology (remote · claims.zicron.ai)

Quote, request and run page-cited medical chronologies for law firms and nurse consultants.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `claims.zicron.ai`: 38/100, [markdown](https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/agent-mcp.md), [page](https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/agent-mcp)
- remote · `claims.zicron.ai`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/claims.md), [page](https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/claims)

## Channel facts

- Endpoint: `https://claims.zicron.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1195 tokens (~239/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Zicron medical chronology MCP server?

Zicron medical chronology is a hosted endpoint at https://claims.zicron.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "ai-zicron-claims-medical-chronology": {
      "url": "https://claims.zicron.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-zicron-claims-medical-chronology": {
      "type": "http",
      "url": "https://claims.zicron.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-zicron-claims-medical-chronology]
url = "https://claims.zicron.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-zicron-claims-medical-chronology": {
      "type": "remote",
      "url": "https://claims.zicron.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-zicron-claims-medical-chronology --url 'https://claims.zicron.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-zicron-claims-medical-chronology:
    url: "https://claims.zicron.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-zicron-claims-medical-chronology": {
      "Transport": "http",
      "Url": "https://claims.zicron.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-zicron-claims-medical-chronology -t streamable-http -u 'https://claims.zicron.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-zicron-claims-medical-chronology": {
      "type": "http",
      "url": "https://claims.zicron.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 73)

First indexed and scored.

## MCP tools (5)

### `get_offer` (~136 tokens)

Get Zicron's medical chronology offer

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, 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.

### `quote_chronology` (~155 tokens)

Quote a medical chronology by page count

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.

Input parameters:

- `first_case` (boolean): True if this would be the requester's first case with Zicron (first case is half price).
- `pages` (integer, required): Approximate total number of pages in the medical record set.

### `request_chronology` (~535 tokens)

Request a medical chronology (contact request, no records)

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.

Input parameters:

- `agent_name` (string): Name of the AI assistant or agent making this request (e.g. "Claude", "ChatGPT"). Optional.
- `case_type` (string, required): Type of case the chronology is for.
- `confirmed_by_user` (boolean, required): 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.
- `deadline` (string): When the chronology is needed back, YYYY-MM-DD (optional).
- `dry_run` (boolean): If true, validate and return the estimate without sending the request.
- `estimated_pages` (integer): Approximate total page count of the records (optional; used for the estimate).
- `firm_name` (string): Law firm or LNC business name (optional).
- `idempotency_key` (string): Optional key; repeating a call with the same key and details returns the original request.
- `is_first_case` (boolean): Whether this is the requester's first case with Zicron (half price). Defaults to true.
- `notes` (string): 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…
- `phone` (string): Requester's phone number (optional).
- `requester_email` (string, required): Email address Zicron should reply to with the quote and secure upload link.
- `requester_name` (string, required): Name of the attorney, LNC or staff member Zicron should reply to. Not the patient.
- `requester_role` (string, required): The requester's role.

### `get_sample_chronology` (~73 tokens)

Get a sample Zicron medical chronology

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.

### `get_ssdi_pilot_info` (~111 tokens)

Get Zicron's SSDI intake-scoring pilot for firms

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/claims#diagnostics

## Score history

- 2026-09-27: 73

## Common questions

### What is the Zicron medical chronology MCP server?

Zicron medical chronology is an MCP server listed in the public MCP registry as ai.zicron.claims/medical-chronology. Quote, request and run page-cited medical chronologies for law firms and nurse consultants. This page covers its hosted endpoint (https://claims.zicron.ai/mcp).

### Is the Zicron medical chronology MCP server safe to use?

Zicron medical chronology scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Zicron medical chronology MCP server expose?

Zicron medical chronology exposes 5 tools: get_offer, quote_chronology, request_chronology, get_sample_chronology, get_ssdi_pilot_info. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.

### Does the Zicron medical chronology MCP server require authentication?

No. We connected to Zicron medical chronology without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zicron medical chronology MCP server still maintained?

Zicron medical chronology is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://claims.zicron.ai/mcp
- Website: https://claims.zicron.ai/medical-chronology
- Changelog RSS feed: https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/claims.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/claims.json
- HTML version of this page: https://verifymcp.io/servers/ai-zicron-claims-medical-chronology/claims