NestDaddy

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

Terminal
claude mcp add --transport http postfact https://postfact-api-production.up.railway.app/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "postfact": {
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "postfact": {
      "type": "http",
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://postfact-api-production.up.railway.app/mcp

Tools 1 found in our last check

  • 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.

Details

Endpointhttps://postfact-api-production.up.railway.app/mcp (Streamable HTTP)
First published13 Sep 2026
Last updated13 Sep 2026
Registry nameio.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.