# Settlement Engine (remote · mcp.viridisconservation.com)

Progressive settlement for outcome-based capital: what is decided, what the remainder must do.

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

## Components

- remote · `mcp.viridisconservation.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/jdhart81-settlement-engine/settlement-engine-mcp.md), [page](https://verifymcp.io/servers/jdhart81-settlement-engine/settlement-engine-mcp)

## Channel facts

- Endpoint: `https://mcp.viridisconservation.com/settlement-engine/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (register_series).
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1014 tokens (~84/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Settlement Engine MCP server?

Settlement Engine is a hosted endpoint at https://mcp.viridisconservation.com/settlement-engine/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http jdhart81-settlement-engine 'https://mcp.viridisconservation.com/settlement-engine/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jdhart81-settlement-engine": {
      "url": "https://mcp.viridisconservation.com/settlement-engine/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jdhart81-settlement-engine": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/settlement-engine/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jdhart81-settlement-engine]
url = "https://mcp.viridisconservation.com/settlement-engine/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jdhart81-settlement-engine": {
      "type": "remote",
      "url": "https://mcp.viridisconservation.com/settlement-engine/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jdhart81-settlement-engine --url 'https://mcp.viridisconservation.com/settlement-engine/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jdhart81-settlement-engine:
    url: "https://mcp.viridisconservation.com/settlement-engine/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jdhart81-settlement-engine": {
      "Transport": "http",
      "Url": "https://mcp.viridisconservation.com/settlement-engine/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jdhart81-settlement-engine -t streamable-http -u 'https://mcp.viridisconservation.com/settlement-engine/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jdhart81-settlement-engine": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/settlement-engine/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-11-21 (score 68, +1)

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

### 2026-11-19 (score 67, +1)

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

### 2026-11-17 (score 66, +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-11-16 (score 65, +4)

- [functional regression] Schema quality: 66 → 84
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: fair → good
- [cosmetic] “compile_contract” reworded the description of “closes_at”
- [cosmetic] “compile_contract” reworded the description of “parties”
- [cosmetic] “compile_contract” reworded the description of “rule”
- [cosmetic] “compile_contract” reworded the description of “series_id”
- [cosmetic] “compile_contract” reworded the description of “strike”
- [cosmetic] “compile_contract” reworded the description of “terms”
- [cosmetic] “explain” reworded the description of “series_id”
- [cosmetic] “get_contract” reworded the description of “contract_id”
- [cosmetic] “ingest” reworded the description of “observations”
- [cosmetic] “ingest” reworded the description of “series_id”
- [cosmetic] “period_status” reworded the description of “series_id”
- [cosmetic] “register_series” reworded the description of “aggregate”
- [cosmetic] “register_series” reworded the description of “meta”
- [cosmetic] “register_series” reworded the description of “n_expected”
- [cosmetic] “register_series” reworded the description of “name”
- [cosmetic] “register_series” reworded the description of “period_end”
- [cosmetic] “register_series” reworded the description of “period_start”
- [cosmetic] “register_series” reworded the description of “source”
- [cosmetic] “register_series” reworded the description of “strikes”
- [cosmetic] “register_series” reworded the description of “unit”
- [cosmetic] “register_series” reworded the description of “value_max”
- [cosmetic] “register_series” reworded the description of “value_min”
- [cosmetic] “required_remainder” reworded the description of “series_id”
- [cosmetic] “required_remainder” reworded the description of “strike”
- [cosmetic] “settle_contract” reworded the description of “contract_id”
- [cosmetic] “settle_contract” reworded the description of “now”
- [cosmetic] “verify_settlement” reworded the description of “settlement”
- [cosmetic] “verify_settlement” reworded the description of “settlement_id”

### 2026-11-15 (score 61, +1)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

### 2026-11-13 (score 60, +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-11-11 (score 59, +1)

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

### 2026-11-10 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (12)

### `register_series` (~239 tokens)

Register series

FREE: declare a progressively published series. aggregate: mean (prices), sum (totals), share (survival/success 0/1 per
    slot), last (closing value). n_expected: number of observation slots in the period. value_min/value_max: the physical
    bounds of one observation; without them nothing is decided until the period is complete (S5).

Input parameters:

- `aggregate` (string, required): mean, sum, share or last.
- `meta`: Optional. Extra description of the series.
- `n_expected` (integer, required): Number of observation slots in the period.
- `name` (string, required): Name of the series.
- `period_end` (string, required): Period end, ISO-8601.
- `period_start` (string, required): Period start, ISO-8601.
- `source` (string, required): Where observations are published.
- `strikes`: Optional. Values of interest for the aggregate.
- `unit` (string, required): Unit of one observation, for example USD or percent.
- `value_max`: Optional. Highest physically possible value of one observation.
- `value_min`: Optional. Lowest physically possible value of one observation.

Output parameters:

- `result` (string)

### `ingest` (~98 tokens)

Ingest

FREE: append observations [{slot, value, source_url, source_sha256 (64 hex of the source document), observed_at}].
    A re-posted slot replaces the value and is logged as a revision (S7). Each observation is hashed (S4).

Input parameters:

- `observations` (array, required): [{slot, value, source_url, source_sha256, observed_at}].
- `series_id` (string, required): The series id returned by register_series.

Output parameters:

- `result` (string)

### `period_status` (~68 tokens)

Period status

FREE: published share, published aggregate, remaining slots, and per strike the required remainder, the decided
    flag (arithmetic + declared bounds only) and a labelled model estimate kept separate from the facts (S1).

Input parameters:

- `series_id` (string, required): The series id returned by register_series.

Output parameters:

- `result` (string)

### `required_remainder` (~58 tokens)

Required remainder

FREE: what the remaining slots must average / sum to / hit for the aggregate to reach the strike, plus decided.

Input parameters:

- `series_id` (string, required): The series id returned by register_series.
- `strike` (number, required): The strike value.

Output parameters:

- `result` (string)

### `decided_strikes` (~25 tokens)

Decided strikes

FREE: every strike across registered series that is decided by the published part alone.

Output parameters:

- `result` (string)

### `explain` (~40 tokens)

Explain

FREE: deterministic plain-language reading of a series (no LLM in the serving path).

Input parameters:

- `series_id` (string, required): The series id returned by register_series.

Output parameters:

- `result` (string)

### `list_series` (~14 tokens)

List series

FREE: registered series cards.

Output parameters:

- `result` (string)

### `compile_contract` (~151 tokens)

Compile contract

PAID: compile a Verified Outcome Contract v0 — a series, a strike, a settlement rule (above | at_or_above | below |
    at_or_below) and a closing time, content-addressed; the contract_id is the sha256 of its canonical form.

Input parameters:

- `closes_at` (string, required): When the contract closes, ISO-8601.
- `parties`: Optional. The parties, as an object.
- `rule` (string, required): above, at_or_above, below or at_or_below.
- `series_id` (string, required): The series id returned by register_series.
- `strike` (number, required): The strike value.
- `terms`: Optional. Contract terms in words.

Output parameters:

- `result` (string)

### `get_contract` (~33 tokens)

Get contract

FREE: a compiled contract and its settlement ids.

Input parameters:

- `contract_id` (string, required): The contract id returned by compile_contract.

Output parameters:

- `result` (string)

### `settle_contract` (~113 tokens)

Settle contract

PAID: evaluate a contract against the ledger at an explicit time: YES / NO / UNDECIDED with the exact arithmetic and
    every observation hash used. A decided strike settles before closure; an incomplete, undecided series at closure is
    UNDECIDED, never a guess (S10). Settlements are immutable and recomputable (S8).

Input parameters:

- `contract_id` (string, required): The contract id returned by compile_contract.
- `now` (string, required): The evaluation time, ISO-8601.

Output parameters:

- `result` (string)

### `verify_settlement` (~59 tokens)

Verify settlement

FREE: recompute a settlement from its stored evidence (hash, aggregate, result each checked separately).

Input parameters:

- `settlement`: A settlement object; give this or settlement_id.
- `settlement_id`: A settlement id; give this or the settlement object.

Output parameters:

- `result` (string)

### `describe_agent` (~22 tokens)

Describe this service

FREE: actions, invariants S1–S10 and limits.

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 65
- 2026-11-15: 61
- 2026-11-14: 60
- 2026-11-13: 60
- 2026-11-12: 59
- 2026-11-11: 59
- 2026-11-10: 58
- 2026-11-09: 58

## Common questions

### What is the Settlement Engine MCP server?

Settlement Engine is an MCP server listed in the public MCP registry as io.github.jdhart81/settlement-engine. Progressive settlement for outcome-based capital: what is decided, what the remainder must do. This page covers its hosted endpoint (https://mcp.viridisconservation.com/settlement-engine/mcp).

### Is the Settlement Engine MCP server safe to use?

Settlement Engine scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Settlement Engine MCP server expose?

Settlement Engine exposes 12 tools: register_series, ingest, period_status, required_remainder, decided_strikes, and 7 more. Their descriptions and schemas cost roughly 920 tokens of context every time the server is loaded.

### Does the Settlement Engine MCP server require authentication?

No. We connected to Settlement Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Settlement Engine MCP server still maintained?

Settlement Engine is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Settlement Engine MCP server?

VerifyMCP ran 13 checks on Settlement Engine, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.viridisconservation.com/settlement-engine/mcp
- Repository: https://github.com/jdhart81/viridis-agent-fleet
- Website: https://github.com/jdhart81/viridis-agent-fleet/blob/main/docs/servers/settlement-engine.md
- Changelog RSS feed: https://verifymcp.io/servers/jdhart81-settlement-engine/settlement-engine-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jdhart81-settlement-engine/settlement-engine-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/jdhart81-settlement-engine/settlement-engine-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jdhart81-settlement-engine/settlement-engine-mcp
