AllClear Connect (OAuth, OIDC, and MCP)

com.allclearidPublished by allclearid.comOfficial publisherv1.0.0Updated Oct 26, 2026

Verified identity plus consented personal context, starting with medical records, images & insurance

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote AllClear Connect server that gives an assistant verified identity plus consented personal context, starting with medical records, images and insurance.

What you can do
  • Provides verified identity information about the user.
  • Supplies consented personal context, starting with medical records, images and insurance.
  • No tool list is published, so the exact operations an assistant can call are not documented here.
When to use it
When an assistant needs identity-verified personal context, such as medical records, images or insurance details, rather than general web or file access.
Requirements
Remote streamable HTTP endpoint at mcp.app.allclearid.com; OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server handles sensitive personal data, including medical records and insurance information, and requires OAuth sign-in. Only connect if you trust the provider and are comfortable granting access to that data; the published tool list is empty, so review what it can access after connecting.

Installation

In SourceWeft

  1. Open AllClear Connect (OAuth, OIDC, and MCP) 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/com.allclearid%2Fconnect/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": {
    "allclear-connect-oauth-oidc-and": {
      "type": "http",
      "url": "https://mcp.app.allclearid.com/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 21, 2026

Score

56% 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

    Publish an icon in the registry entry.

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