Futility Breaker

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.textforagents/futility-breaker-evidence-bound-stopping and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 22 Oct 2026. Not supplied by the maker.

• futility_register_run

  Register a run with its alternatives and operator-registered source identities (strings or {id, aliases}) before judging.

• futility_judge

  Record one usefulness judgment (useful / useless / partial) for a run/source/domain and return the binding verdict (CONTINUE / STOP-SOURCE / INTEGRATE-NOW / ABSTAIN). Billed as a verdict call: one-tim

• futility_verdict

  Read the current verdict for a run/source/domain without recording a judgment.

• futility_waste_report

  Waste report for a run: tokens spent after the verdict point, per source and per domain aggregate.

• futility_receipt

  Mint the HMAC-signed abstention receipt when the run/source/domain verdict is ABSTAIN.

• futility_verify_receipt

  Verify a receipt payload {receipt, signature}; total rejection with a reason on malformed/forged input.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.