POSTFACT — Resolve Ambiguous Side Effects Before Retry

io.github.GSterlingPress/postfact

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

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Cursor · HTTP clients.

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

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.1.1
Registry
active
Published
9/13/2026

Remotes

  • streamable-httphttps://postfact-api-production.up.railway.app/mcp
Browse all Developer Tools →

Add the badge to your site

Show visitors that POSTFACT — Resolve Ambiguous Side Effects Before Retry is listed here — it’s also the link we check for a free listing.

POSTFACT — Resolve Ambiguous Side Effects Before Retry — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-gsterlingpress-postfact?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="POSTFACT — Resolve Ambiguous Side Effects Before Retry — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![POSTFACT — Resolve Ambiguous Side Effects Before Retry — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-gsterlingpress-postfact?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.