_ registry / mcp streamable-http · checked 5h ago

zicron-medical-chronology

https://claims.zicron.ai

Registry code: c6c21ae11d91d65e

api record

Zicron AI turns medical records into page-cited work product for legal and claims teams. This public server needs no sign-in and accepts no patient information. It describes Zicron's done-for-you medical chronology (a case summary plus one timeline across every provider, each entry cited to its page, in 48 hours, $450 per case up to 1,000 pages, first case refundable if it isn't usable), quotes a price, shows a sample and sends a contact request. Start with get_offer. To work on records inside a Zicron account (create a case, upload records through signed upload links, generate and read the…

endpoint
https://claims.zicron.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is zicron-medical-chronology live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is zicron-medical-chronology free to use?
Yes — the hub reached it with no key and no payment.
What tools does zicron-medical-chronology have?
5 tools: request_chronology, quote_chronology, get_sample_chronology, get_offer, get_ssdi_pilot_info.
Is zicron-medical-chronology safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
166ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 293 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get a quote for a medical chronology
  • see a sample medical chronology
  • request a medical chronology for a case
takes → gives
text → data, text
tools
4 reads1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_sample_chronology reads open 26h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_offer reads open 26h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_ssdi_pilot_info reads open 26h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • request_chronology sends messages unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "requester_name",
        "requester_email",
        "requester_role",
        "case_type",
        "confirmed_by_user"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "maxLength": 500,
          "description": "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": {
          "type": "string",
          "maxLength": 40,
          "description": "Requester's phone number (optional)."
        },
        "dry_run": {
          "type": "boolean",
          "default": false,
          "description": "If true, validate and return the estimate without sending the request."
        },
        "deadline": {
          "type": "string",
          "format": "date",
          "description": "When the chronology is needed back, as YYYY-MM-DD, e.g. 2026-11-15 (optional)."
        },
        "case_type": {
          "enum": [
            "personal_injury",
            "medical_malpractice",
            "nursing_home",
            "workers_comp",
            "other"
          ],
          "type": "string",
          "description": "Type of case the chronology is for."
        },
        "firm_name": {
          "type": "string",
          "maxLength": 160,
          "description": "Law firm or LNC business name (optional)."
        },
        "agent_name": {
          "type": "string",
          "maxLength": 80,
          "description": "Name of the AI assistant or agent making this request (e.g. \"Claude\", \"ChatGPT\"). Optional."
        },
        "is_first_case": {
          "type": "boolean",
          "default": true,
          "description": "Whether this is the requester's first case with Zicron (half price). Defaults to true."
        },
        "requester_name": {
          "type": "string",
          "maxLength": 120,
          "description": "Name of the attorney, LNC or staff member Zicron should reply to. Not the patient."
        },
        "requester_role": {
          "enum": [
            "legal_nurse_consultant",
            "lnc_firm",
            "pi_attorney",
            "medmal_attorney",
            "nursing_home_attorney",
            "paralegal",
            "other"
          ],
          "type": "string",
          "description": "The requester's role."
        },
        "estimated_pages": {
          "type": "integer",
          "maximum": 100000,
          "minimum": 1,
          "description": "Approximate total page count of the records (optional; used for the estimate)."
        },
        "idempotency_key": {
          "type": "string",
          "maxLength": 100,
          "description": "Optional key; repeating a call with the same key and details returns the original request."
        },
        "requester_email": {
          "type": "string",
          "format": "email",
          "maxLength": 254,
          "description": "Email address Zicron should reply to with the quote and secure upload link."
        },
        "confirmed_by_user": {
          "type": "boolean",
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 98 lines
  • quote_chronology reads unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "pages"
      ],
      "properties": {
        "pages": {
          "type": "integer",
          "maximum": 100000,
          "minimum": 1,
          "description": "Approximate total number of pages in the medical record set."
        },
        "first_case": {
          "type": "boolean",
          "default": false,
          "description": "True if this would be the requester's first case with Zicron (first case is half price)."
        }
      },
      "additionalProperties": true
    }
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c6c21ae11d91d65e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c6c21ae11d91d65e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c6c21ae11d91d65e/badge.svg)](https://brick.blue/agent/c6c21ae11d91d65e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.