Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Settlement Engine

REMOTE · MCP.VIRIDISCONSERVATION.COM

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

+8 this week 68 Trust /100

Last scanned (19 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1014 tokens (~84/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 16 Nov 26 +4
    • Schema quality: 66 → 84 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: fair → good functional
    • “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” cosmetic
  • 15 Nov 26 +1
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.viridisconservation.com/settlement-engine/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.viridisconservation.com CN=YE2,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA384 53c256f29f603e6cc54aff3493f1ae10509
SANs: mcp.viridisconservation.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.viridisconservation.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
viridisconservation.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.viridisconservation.com/settlement-engine/mcp Verified 200
http (plaintext) http://mcp.viridisconservation.com/settlement-engine/mcp HTTPS enforced 308 https://mcp.viridisconservation.com/settlement-engine/mcp
MCP tools · 12 exposed · ~920 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compile_contract ~151

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.

NameTypeReqDescription
closes_atstringyesWhen the contract closes, ISO-8601.
parties––Optional. The parties, as an object.
rulestringyesabove, at_or_above, below or at_or_below.
series_idstringyesThe series id returned by register_series.
strikenumberyesThe strike value.
terms––Optional. Contract terms in words.
NameTypeReqDescription
resultstringyes–

No examples provided.

decided_strikes ~25

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

describe_agent ~22

FREE: actions, invariants S1–S10 and limits.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

explain ~40

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

NameTypeReqDescription
series_idstringyesThe series id returned by register_series.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_contract ~33

FREE: a compiled contract and its settlement ids.

NameTypeReqDescription
contract_idstringyesThe contract id returned by compile_contract.
NameTypeReqDescription
resultstringyes–

No examples provided.

ingest ~98

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).

NameTypeReqDescription
observationsarrayyes[{slot, value, source_url, source_sha256, observed_at}].
series_idstringyesThe series id returned by register_series.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_series ~14

FREE: registered series cards.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

period_status ~68

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).

NameTypeReqDescription
series_idstringyesThe series id returned by register_series.
NameTypeReqDescription
resultstringyes–

No examples provided.

register_series ~239

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).

NameTypeReqDescription
aggregatestringyesmean, sum, share or last.
meta––Optional. Extra description of the series.
n_expectedintegeryesNumber of observation slots in the period.
namestringyesName of the series.
period_endstringyesPeriod end, ISO-8601.
period_startstringyesPeriod start, ISO-8601.
sourcestringyesWhere observations are published.
strikes––Optional. Values of interest for the aggregate.
unitstringyesUnit 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.
NameTypeReqDescription
resultstringyes–

No examples provided.

required_remainder ~58

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

NameTypeReqDescription
series_idstringyesThe series id returned by register_series.
strikenumberyesThe strike value.
NameTypeReqDescription
resultstringyes–

No examples provided.

settle_contract ~113

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).

NameTypeReqDescription
contract_idstringyesThe contract id returned by compile_contract.
nowstringyesThe evaluation time, ISO-8601.
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_settlement ~59

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

NameTypeReqDescription
settlement––A settlement object; give this or settlement_id.
settlement_id––A settlement id; give this or the settlement object.
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

remote · mcp.viridisconservation.com

# add to Claude Code
claude mcp add --transport http jdhart81-settlement-engine 'https://mcp.viridisconservation.com/settlement-engine/mcp'
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.