Lets an assistant record signed self-forecasts tied to a run, resolve them against actual outcomes, and query calibration scores and a trust weight.
What you can do
Record a signed forecast bound to a run ID, with probability, cost and duration estimates
Resolve a forecast against its run record, supplying success, actual cost and actual duration
Query calibration metrics for a forecaster and cohort: Brier score, skill versus climatology, bins, cost and duration error
Read the trust weight or kill state for a forecaster and cohort
When to use it
Useful when you want an agent's predictions about its own runs logged and later scored, for example to compare forecasters within a cohort or to gate an agent on measured calibration rather than self-reported confidence.
Requirements
A remote endpoint at textforagents.com over streamable HTTP. An api_token obtained from a registration endpoint is required by every tool, along with forecaster, cohort and run_id values. No environment variables or headers are declared.
Before you install
Resolving a forecast is billed at $0.01 per forecast and calibration queries at $0.005, with one free 100-forecast batch per operator; an optional x_payment value is accepted. The api_token is a credential and should be kept private. Forecasts and run outcomes are sent to a third-party service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.textforagents%2Fforecast-calibration-ledger/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Resolve a forecast against its run record ($0.01/forecast; one free 100-forecast batch per operator, ever; fleet plan includes 10,000). Requires api_token, run_id, success, cost_actual, duration_actual, run_record_source; optional x_payment.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.