# operant-mcp (remote · operant-mcp.saagar210.workers.dev)

Read-only MCP server for the OPERANT AI operating-agent calibration benchmark.

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

## Components

- remote · `operant-mcp.saagar210.workers.dev`: 64/100 (this document), [markdown](https://verifymcp.io/servers/saagpatel-operant-mcp/operant-mcp.md), [page](https://verifymcp.io/servers/saagpatel-operant-mcp/operant-mcp)
- npm · `saagar-operant-mcp`: 69/100, [markdown](https://verifymcp.io/servers/saagpatel-operant-mcp/saagar-operant-mcp.md), [page](https://verifymcp.io/servers/saagpatel-operant-mcp/saagar-operant-mcp)

## Channel facts

- Endpoint: `https://operant-mcp.saagar210.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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**: 46/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 5 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 not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 82/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 637 tokens (~91/item across 7 items; 5 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 saagpatel-operant-mcp https://operant-mcp.saagar210.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.saagpatel-operant-mcp]
url = "https://operant-mcp.saagar210.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "saagpatel-operant-mcp": {
      "type": "remote",
      "url": "https://operant-mcp.saagar210.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add saagpatel-operant-mcp --url https://operant-mcp.saagar210.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  saagpatel-operant-mcp:
    url: "https://operant-mcp.saagar210.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "saagpatel-operant-mcp": {
      "type": "http",
      "url": "https://operant-mcp.saagar210.workers.dev/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 64, +1)

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

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

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

### 2026-07-31 (score 62, −3)

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

### 2026-07-30 (score 65, +1)

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

### 2026-07-29 (score 64, +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-07-27 (score 63, +1)

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

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

First indexed and scored.

## MCP tools (5)

### `get_results` (~56 tokens)

Get retained calculation profiles

Return retained model calculation profiles plus generated_at, claim_status, claims_at_risk, and the bounded evidence_binding. These rows are not durable named-model performance claims. Do not rank them or treat stdev/significance as reliable model evidence.

### `compare_models` (~133 tokens)

Inspect two retained profiles

Place two retained calculation profiles side by side by display_name substring. Returns ocs_mean, ocs_stdev, orchestration_mean, run_family, and subject_shell for each, plus comparison_status=NOT_DURABLE and the public claim_status. This is not evidence that either named model outperforms, equals, or differs significantly from the other. If a name is ambiguous or not found, returns an error listing all available display_names.

Input parameters:

- `model_a` (string, required): Display name (or substring) of the first model
- `model_b` (string, required): Display name (or substring) of the second model

### `get_methodology` (~85 tokens)

Get benchmark methodology

Return the benchmark design: the 4 axes, the OCS formula (Youden's J), the 5 decision labels (PROCEED, PROCEED_SANCTIONED, REFUSE, ESCALATE, REROUTE), scoring blocks, and a concise what-it-measures / what-it-doesn't summary. Sourced from the baked case-file metadata.

### `list_cases` (~111 tokens)

List cases

Return case metadata (no full task prompts): pair_id/id, axis, tier, grounding, and side indicators (malign/benign for axes 1/2/4; null for axis 3). Filter by axis, or omit for all cases across all axes (the result includes a count). Use get_case to fetch a full case with task prompts and expected decisions.

Input parameters:

- `axis` (string): Axis to filter by: refusal-calibration | sanctioned-path | orchestration | escalation-reroute

### `get_case` (~122 tokens)

Get a case

Return the full case for a given pair_id (axes 1/2/4) or id (axis 3): malign and benign task prompts, expected decisions, grounding rationale, and bypass patterns. Axis 3 cases are single (unmatched) and use an 'id' field instead of 'pair_id'. Use list_cases to browse available ids.

Input parameters:

- `axis` (string, required): The axis this case belongs to
- `pair_id` (string, required): The pair_id (axes 1/2/4) or id (axis 3) to retrieve

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://operant-mcp.saagar210.workers.dev/mcp
- Repository: https://github.com/saagpatel/operant
- Changelog RSS feed: https://verifymcp.io/servers/saagpatel-operant-mcp/operant-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/saagpatel-operant-mcp/operant-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/saagpatel-operant-mcp/operant-mcp