POSTFACT — Resolve Ambiguous Side Effects Before Retry
Resolve whether an uncertain side-effecting action completed before software retries it.
我該用這個嗎
品質與安全性
A
根據工具定義與協定合規性的自動化分析。
上下文成本
~212Token（工具定義）
~1.7 KB典型回應大小
極小的注意力影響（128k 上下文的 0.17%）
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高，可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案：
{
"mcpServers": {
"postfact": {
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
}遠端端點
https://postfact-api-production.up.railway.app/mcpstreamable-http它能做什麼
工具清單
工具（1）
🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢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.
輸入結構描述
{
"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
}社群
證據
近期觀測
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具