mcpbeat Sign in

Settlement Engine MCP Server

by jdhart81 Your server? Claim it
answering

Settlement Engine is answering right now. Last checked 12 min ago. It exposes 12 tools. Last commit 9 Nov 2026.

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

Uptime history 25 hours of history
25 hours agonow
100.0%
Uptime 24h
90 of 90 checks
12
Tools
read from the server
349 ms
Response time
average over 24h
0
Stars
last commit 9 Nov 2026

Nothing serious here today

Today is the operative word: we check Settlement Engine every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add settlement-engine --transport http https://mcp.viridisconservation.com/settlement-engine/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.viridisconservation.com/settlement-engine/mcp
~/.codex/config.toml
[mcp_servers.settlement-engine]
url = "https://mcp.viridisconservation.com/settlement-engine/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "settlement-engine": {
      "url": "https://mcp.viridisconservation.com/settlement-engine/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "settlement-engine": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/settlement-engine/mcp"
    }
  }
}

Available tools 12

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

compile
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.
contract
get_contract
FREE: a compiled contract and its settlement ids.
decided
decided_strikes
FREE: every strike across registered series that is decided by the published part alone.
describe
describe_agent
FREE: actions, invariants S1–S10 and limits.
explain
explain
FREE: deterministic plain-language reading of a series (no LLM in the serving path).
ingest
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).
period
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).
register
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).
required
required_remainder
FREE: what the remaining slots must average / sum to / hit for the aggregate to reach the strike, plus decided.
series
list_series
FREE: registered series cards.
settle
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).
verify
verify_settlement
FREE: recompute a settlement from its stored evidence (hash, aggregate, result each checked separately).

Endpoints

URLTransportStateLatencyChecked
https://mcp.viridisconservation.com/settlement-engine/mcp streamable-http answering 328 ms 12 min ago

Alternatives to Settlement Engine

same job, measured the same way
Agent-Carried Work History
by textforagents

Your agent carries its own resume — outcome receipts minted at settlement, held by the agent.

7 tools answering
NEUS MCP
by neus

The trust harness for AI agents. Set what an agent can do before it acts.

12 tools answering
P402
by z333q

Multi-provider AI router with x402 micropayment settlement on Base L2. 1% flat fee.

55 installs/wk local only
Startup Name Check
by openkrill

Check whether the domain for a startup, product or business name is already registered.

3 tools answering
S
socseal settlement door
by socseal

Read-only settlement proof for agents: prove a txid MINED, post-quantum signed. Fail-closed.

local only
Amomic-AI Docs
by amomic

Search the Amomic-AI docs and REST API for AI agents on calls, WhatsApp, chat and email.

3 tools answering
getorderability: AIO orderability door
by allooloo

AIO orderability: may a capital product be ordered for a client category? Signed by the home node.

7 tools answering
Office Oxide MCP
by aimino-tech

Rust-native MCP server for Office document processing

83 installs/wk local only

Settlement Engine — questions

Answers built from our own checks of this server.

What can Settlement Engine do?
It exposes 12 tools, read directly from the server on our last check. Among them: compile_contract, decided_strikes, describe_agent, explain, get_contract, ingest and 6 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 Settlement Engine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 349 ms. The bar chart above shows every period we have measured.
How do I connect Settlement Engine?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Settlement Engine need an API key?
No. Settlement Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Settlement Engine?
It answers our handshake in 349 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Settlement Engine open source?
The code is open source: it is published under the Apache-2.0 licence, written in Python, 0 stars on GitHub and 4 open issues. The licence covers the code in the repository, not the hosted service at mcp.viridisconservation.com, which runs on its operator's own terms.