# io.sentinelsignal/scoring (remote · mcp.sentinelsignal.io)

Hosted MCP for denial, prior auth, reimbursement, workflow validation, batch scoring, and feedback.

- Trust score: 68/100 (medium)
- Change this week: +65
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.sentinelsignal.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-sentinelsignal-scoring/mcp.md), [page](https://verifymcp.io/servers/io-sentinelsignal-scoring/mcp)

## Channel facts

- Endpoint: `https://mcp.sentinelsignal.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.6`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 480 tokens (~60/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-sentinelsignal-scoring https://mcp.sentinelsignal.io/mcp
```

### Codex

```toml
[mcp_servers.io-sentinelsignal-scoring]
url = "https://mcp.sentinelsignal.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-sentinelsignal-scoring": {
      "type": "remote",
      "url": "https://mcp.sentinelsignal.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-sentinelsignal-scoring --url https://mcp.sentinelsignal.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-sentinelsignal-scoring:
    url: "https://mcp.sentinelsignal.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-sentinelsignal-scoring": {
      "type": "http",
      "url": "https://mcp.sentinelsignal.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-31 (score 66, +63)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 3, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 3, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 3)

First indexed and scored.

## MCP tools (8)

### `list_workflows` (~24 tokens)

List supported workflows and current model versions via GET /v1/workflows

### `get_workflow_schema` (~62 tokens)

Fetch required fields, optional fields, enums, and an example payload for a workflow via GET /v1/workflows/{workflow}/schema

Input parameters:

- `workflow` (string, required): Workflow identifier such as healthcare.denial, healthcare.prior_auth, or healthcare.reimbursement.

### `validate_workflow_payload` (~70 tokens)

Validate and normalize a workflow payload without consuming a scoring call via POST /v1/workflows/{workflow}/validate

Input parameters:

- `payload` (object, required): Workflow payload to validate before scoring.
- `workflow` (string, required): Workflow identifier such as healthcare.denial, healthcare.prior_auth, or healthcare.reimbursement.

### `score_workflow` (~83 tokens)

Score Sentinel healthcare workflows via POST /v1/score

Input parameters:

- `options` (object|null): Optional scoring flags such as explanation or threshold controls.
- `payload` (object, required): Structured workflow payload matching Sentinel /v1/score for the selected workflow.
- `workflow` (string, required): Workflow identifier such as healthcare.denial, healthcare.prior_auth, or healthcare.reimbursement.

### `score_batch` (~72 tokens)

Score up to 25 workflow items sequentially in one request via POST /v1/score/batch

Input parameters:

- `continue_on_error` (boolean): When true, later items continue even if an earlier item fails.
- `items` (array, required): List of scoring items, each containing workflow, payload, and optional options.

### `get_limits` (~26 tokens)

Retrieve plan limits, trial quota, and upgrade state via GET /v1/limits

### `get_usage` (~35 tokens)

Retrieve monthly scoring call usage via GET /v1/usage

Input parameters:

- `month` (string): Optional billing month in YYYY-MM format.

### `submit_feedback` (~37 tokens)

Submit structured claims outcome feedback via POST /v1/feedback

Input parameters:

- `feedback` (object, required): Structured feedback payload for a prior Sentinel scoring event.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-sentinelsignal-scoring/mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 3
- 2026-07-29: 3
- 2026-07-28: 3
- 2026-07-27: 3
- 2026-07-26: 3

## Links

- Remote endpoint: https://mcp.sentinelsignal.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-sentinelsignal-scoring/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-sentinelsignal-scoring/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-sentinelsignal-scoring/mcp