Zicron medical chronology
REMOTE · CLAIMS.ZICRON.AI · 2 COMPONENTS · SCANNED SEP 27
Quote, request and run page-cited medical chronologies for law firms and nurse consultants.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
remote · claims.zicron.ai
claude mcp add --transport http ai-zicron-claims-medical-chronology 'https://claims.zicron.ai/mcp'
{
"mcpServers": {
"ai-zicron-claims-medical-chronology": {
"url": "https://claims.zicron.ai/mcp"
}
}
} {
"servers": {
"ai-zicron-claims-medical-chronology": {
"type": "http",
"url": "https://claims.zicron.ai/mcp"
}
}
} [mcp_servers.ai-zicron-claims-medical-chronology] url = "https://claims.zicron.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-zicron-claims-medical-chronology": {
"type": "remote",
"url": "https://claims.zicron.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-zicron-claims-medical-chronology --url 'https://claims.zicron.ai/mcp' --transport streamable-http
mcp_servers:
ai-zicron-claims-medical-chronology:
url: "https://claims.zicron.ai/mcp" {
"McpServers": {
"ai-zicron-claims-medical-chronology": {
"Transport": "http",
"Url": "https://claims.zicron.ai/mcp"
}
}
} assistant mcp add ai-zicron-claims-medical-chronology -t streamable-http -u 'https://claims.zicron.ai/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://claims.zicron.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=claims.zicron.ai | CN=WR3,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | RSA 2048 | SHA256-RSA | b0a0bacdc00be1ab102360a0589a7650 |
| SANs: claims.zicron.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of claims.zicron.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| zicron.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https://api.claims.zicron.ai https://*.posthog.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://*.googletagmanager.com https://www.google.com https://*.doubleclick.net https://*.g.doubleclick.net https://www.googleadservices.com wss:; frame-src https://www.googletagmanager.com https://*.doubleclick.net; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://claims.zicron.ai/mcp | Verified | 200 | |
| http (plaintext) | http://claims.zicron.ai/mcp | HTTPS enforced | 302 | https://claims.zicron.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_offer Get Zicron's medical chronology offer ~136
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sample_chronology Get a sample Zicron medical chronology ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_ssdi_pilot_info Get Zicron's SSDI intake-scoring pilot for firms ~111
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_chronology Quote a medical chronology by page count ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first_case | boolean | – | True if this would be the requester's first case with Zicron (first case is half price). |
| pages | integer | yes | Approximate total number of pages in the medical record set. |
No output schema declared.
No examples provided.
request_chronology Request a medical chronology (contact request, no records) ~535
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Name of the AI assistant or agent making this request (e.g. "Claude", "ChatGPT"). Optional. |
| case_type | string | yes | Type of case the chronology is for. |
| confirmed_by_user | boolean | yes | 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 | yes | Email address Zicron should reply to with the quote and secure upload link. |
| requester_name | string | yes | Name of the attorney, LNC or staff member Zicron should reply to. Not the patient. |
| requester_role | string | yes | The requester's role. |
No output schema declared.
No examples provided.
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.