POSTFACT — Resolve Ambiguous Side Effects Before Retry
Resolve whether an uncertain side-effecting action completed before software retries it.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~212Tokens (tool definitions)
~1.7 KBTypical response size
Minimal attention impact (0.17% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"postfact": {
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
}Remote endpoints
https://postfact-api-production.up.railway.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢resolve_outcome(method, status, failure, sideEffect, idempotencyKey, ...)
Call 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.
Input Schema
{
"type": "object",
"properties": {
"method": {
"type": "string"
},
"status": {
"type": "integer"
},
"failure": {
"type": "string"
},
"sideEffect": {
"type": "boolean"
},
"idempotencyKey": {
"type": "string"
},
"requestId": {
"type": "string"
},
"resourceRef": {
"type": "string"
},
"transactionRef": {
"type": "string"
},
"evidence": {
"type": "object",
"properties": {
"providerStatus": {
"type": "string"
},
"resourceExists": {
"type": "boolean"
},
"receiptVerified": {
"type": "boolean"
},
"transactionStatus": {
"type": "string"
},
"preExecutionRejection": {
"type": "boolean"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}Community
Evidence
Recent observations
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools