Scoring MCP Server

io.sentinelsignal/scoring

answering

Scoring is answering right now. Last checked 6 min ago. It exposes 8 tools.

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

Uptime history 43 hours of history

43 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

380 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "scoring": {
      "url": "https://mcp.sentinelsignal.io/mcp"
    }
  }
}

~/.codex/config.toml

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

.cursor/mcp.json

{
  "mcpServers": {
    "scoring": {
      "url": "https://mcp.sentinelsignal.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "scoring": {
      "url": "https://mcp.sentinelsignal.io/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

score

score_batch

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

score_workflow

Score Sentinel healthcare workflows via POST /v1/score

limits

get_limits

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

submit

submit_feedback

Submit structured claims outcome feedback via POST /v1/feedback

usage

get_usage

Retrieve monthly scoring call usage via GET /v1/usage

validate

validate_workflow_payload

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

workflow

get_workflow_schema

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

workflows

list_workflows

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

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.sentinelsignal.io/mcp	streamable-http	answering	390 ms	6 min ago

Scoring — questions

Answers built from our own checks of this server.

What can Scoring do?

It exposes 8 tools, read directly from the server on our last check. Among them: get_limits, get_usage, get_workflow_schema, list_workflows, score_batch, score_workflow and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Scoring working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 380 ms. The bar chart above shows every period we have measured.

How do I connect Scoring?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Scoring need an API key?

No. Scoring completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Scoring?

It answers our handshake in 380 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.