POSTFACT — Resolve Ambiguous Side Effects Before Retry

io.github.GSterlingPress/postfactVersion 0.1.1

Resolve whether an uncertain side-effecting action completed before software retries it.

Status

Responds282 msNov 14, 2026, 14:37 UTCAnswered our handshake without sign-in.

We could not refresh it, so this page shows the last copy.

Data from the official MCP Registry, checked by run.zero. How we check

Streamable HTTP

https://postfact-api-production.up.railway.app/mcpResponds282 msNov 14, 2026, 14:37 UTC

No sign-in

claude mcp add --transport http postfact https://postfact-api-production.up.railway.app/mcp

1
2
3

Settings > Connectors > Add custom connector
Name: postfact
Remote MCP server URL: https://postfact-api-production.up.railway.app/mcp

{
  "mcpServers": {
    "postfact": {
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}

code --add-mcp '{"name":"postfact","type":"http","url":"https://postfact-api-production.up.railway.app/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

1 tools

Tools of POSTFACT — Resolve Ambiguous Side Effects Before Retry
	Description		Read-only	Idempotent	Open world
`resolve_outcome`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.	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.	No	Yes	Yes	No

Registry status: Active
Published: Sep 13, 2026
Updated: Sep 13, 2026
Website: https://postfact-api-production.up.railway.app/⁠ (opens in a new tab)
Repository: https://github.com/GSterlingPress/postfact-api⁠ (opens in a new tab)
Categories: Uncategorized
GDPR: Not declared