POSTFACT — Resolve Ambiguous Side Effects Before Retry
io.github.GSterlingPress/postfact · v0.1.1
Resolve whether an uncertain side-effecting action completed before software retries it.
Connect Remote server
claude mcp add --transport http postfact https://postfact-api-production.up.railway.app/mcp
{
"mcpServers": {
"postfact": {
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
}
{
"servers": {
"postfact": {
"type": "http",
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://postfact-api-production.up.railway.app/mcp
Tools 1 found in our last check
resolve_outcomeCall after a side-effecting API/tool action fails ambiguously and before retrying. POSTFACT returns DONE only with affirmative completion evidence, NOT_DONE only with affirmative non-execution evidence, otherwise UNKNOWN. UNKNOWN is the safe default.
Details
| Endpoint | https://postfact-api-production.up.railway.app/mcp (Streamable HTTP) |
| First published | 13 Sep 2026 |
| Last updated | 13 Sep 2026 |
| Registry name | io.github.GSterlingPress/postfact |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
