Assurance MCP server

assurance

Software that reports success does not thereby prove it

Every tool here answers one question about work that has already happened, and refuses to answer it when it cannot. Nothing consults a model. Every result is arithmetic you can recompute yourself.

Start with the sentence that shows what that means in practice:

$ pip install assurance-budget
$ assurance-budget runs.jsonl

0 of 3 runs hit a limit — 1 was going nowhere first

  r-002
      Stopped: 3 rounds repeating fetch(url=api/invoices) and failing the same way
      (timeout) with nothing new read and no part of the goal closer. Continuing would
      spend the rest of this run's budget on the same result.

  Not tested by this log: iterations, retries, seconds. The log carries no events of
  that kind, so this is silence rather than a pass.

Read the last line again. The run passed three of the four limits — and the tool says so is not the same as says nothing. Most software reports the absence of a failure as a success, which is how a check that never ran becomes a green tick. This one names what it could not test, in the same breath as what it could.

That is the whole idea, and it is why these are separate from any product: a claim you can check is worth more than a claim you have to trust.

Three questions, three commands

Each installs on its own. None needs the others, an account, a service, or a network.

Did the work cover what it was supposed to cover?

pip install assurance-cli
assurance check ~/reports

No config and no corpus file — it reads the cadence, the span and what is absent from the filenames. A folder with no regular cadence is told so rather than handed a ratio.

Where did the run's budget go, and where did it go nowhere?

pip install assurance-budget
assurance-budget runs.jsonl --fail-on-exhausted

The expensive runs are rarely the ones that crash. They are the ones that retried the same failing call fourteen times and finished with a plausible answer and a bill. Ceilings are enforced by code the caller cannot talk out of them.

May this task proceed, for the person who asked?

pip install assurance-authority
assurance-authority team.json

1 of 3 tasks may proceed for the person who asked — 1 moved owner — 1 refused

  team roster      intern-42    proceed
  Q3 margin memo   intern-42    escalate_ownership -> CFO
      Priya (intern) may not receive finance-confidential, and CFO may. The task moves to
      CFO rather than the answer moving to Priya (intern).
  payroll extract  agent-a      refuse
      Drafting agent may not receive payroll, and nobody offered can. The task stops here.

Shortened. The full README is on GitHub.