Zicron workspace (OAuth)

ai.zicron.claimsPublished by claims.zicron.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Zicron account via OAuth: upload records, get page-cited chronologies, score SSDI and other claims.

The publisher's own server: Zicron medical chronology (public)

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Zicron workspace server that lets an assistant upload records, produce page-cited medical chronologies and score SSDI and other claims via OAuth.

What you can do
  • Upload records to a Zicron account.
  • Generate chronologies with page citations.
  • Score SSDI and other claims.
When to use it
Useful when an assistant should work with a Zicron account on claims and medical chronology tasks, such as turning uploaded records into cited chronologies or scoring disability and other claims.
Requirements
Remote streamable HTTP endpoint at claims.zicron.ai; a Zicron account connected through OAuth, which is required. No environment variables or headers are declared.
Before you install
The server handles uploaded records and claim data, which may include sensitive medical or personal information, and sends them to a third-party service. Uploading records and scoring claims change data in the Zicron account. Review what the assistant may upload or submit before connecting.

Installation

In SourceWeft

  1. Open Zicron workspace (OAuth) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.zicron.claims%2Fworkspace/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zicron-workspace-oauth": {
      "type": "http",
      "url": "https://claims.zicron.ai/agent/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 12, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Zicron integrations