Sentinel Signal MCP for Healthcare Claims Scoring

Hosted and local MCP access for healthcare claims workflow scoring, usage, limits, and feedback.

Hosted First

• Hosted remote MCP endpoint: https://mcp.sentinelsignal.io/mcp
• Smithery listing: @sentinelsignal/scoring (https://server.smithery.ai/sentinelsignal/scoring)
• Free no-signup trial key: POST https://token.sentinelsignal.io/v1/keys/trial
• Local package: uvx sentinel-signal-mcp

Quickstart (10 lines)

uvx sentinel-signal-mcp
export SENTINEL_BASE_URL="https://api.sentinelsignal.io"
export SENTINEL_TOKEN_BASE_URL="https://token.sentinelsignal.io"
# Optional: export SENTINEL_API_KEY="ss_live_or_test_api_key_here"
# If omitted, the MCP server auto-mints a trial key

Hosted remote MCP endpoint (Streamable HTTP): https://mcp.sentinelsignal.io/mcp

Smithery hosted listing: @sentinelsignal/scoring (https://server.smithery.ai/sentinelsignal/scoring)

If your MCP client supports remote HTTP MCP, point it at that URL and send Authorization: Bearer <SENTINEL_API_KEY>. For Smithery-hosted connections, the key is forwarded as x-sentinel-api-key.

Claude Desktop (drop-in MCP config)

{
  "mcpServers": {
    "sentinel-signal": {
      "command": "uvx",
      "args": ["sentinel-signal-mcp"],
      "env": {
        "SENTINEL_BASE_URL": "https://api.sentinelsignal.io",
        "SENTINEL_TOKEN_BASE_URL": "https://token.sentinelsignal.io"
      }
    }
  }
}

Cursor (same MCP config shape)

{
  "mcpServers": {
    "sentinel-signal": {
      "command": "uvx",
      "args": ["sentinel-signal-mcp"],
      "env": {
        "SENTINEL_BASE_URL": "https://api.sentinelsignal.io",
        "SENTINEL_TOKEN_BASE_URL": "https://token.sentinelsignal.io"
      }
    }
  }
}

Windsurf can use the same mcpServers block shape.

This package provides a local stdio MCP server, while the hosted remote service exposes the same healthcare claims tools over Streamable HTTP. It supports either:

PyPI: https://pypi.org/project/sentinel-signal-mcp/

• a user-provided SENTINEL_API_KEY, or
• automatic no-signup trial key minting (POST /v1/keys/trial) with secure local credential caching

Skills (MCP Tools)

• list_workflows — list supported workflows and current model versions
• get_workflow_schema — fetch required fields, optional fields, and an example payload for a workflow
• validate_workflow_payload — validate and normalize a workflow payload before scoring
• score_workflow — score denial risk, prior auth, and reimbursement payloads against a named workflow
• score_batch — score up to 25 workflow items in one request
• get_limits — retrieve plan limits for the current key
• get_usage — retrieve usage for a given month
• submit_feedback — submit structured outcome feedback

Quick start (uvx)

1. Install uv (if needed): https://docs.astral.sh/uv/
2. Set env vars (optional SENTINEL_API_KEY; if omitted, the server auto-mints a trial key and caches it):

export SENTINEL_BASE_URL="https://api.sentinelsignal.io"                      # optional (default shown)
export SENTINEL_TOKEN_BASE_URL="https://token.sentinelsignal.io"  # optional (default shown)
# export SENTINEL_API_KEY="ss_live_or_test_api_key_here"                       # optional
export SENTINEL_TIMEOUT_SECONDS="30"                                           # optional

3. Run the MCP server:

uvx sentinel-signal-mcp

Deliverable behavior: install tool -> (optionally set env vars) -> agent can call score_workflow.

If no API key is configured, the MCP server resolves credentials in this order:

1. SENTINEL_API_KEY env var
2. cached trial key (~/.sentinel/credentials.json by default) if not expired and base URLs match
3. mint a new trial key from `POST {SENTINEL_TOKEN_BASE_URL}/v1/keys/tri

... View full README on GitHub