POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP Server

by gsterlingpress Your server? Claim it

answering

POSTFACT — Resolve Ambiguous Side Effects Before Retry is answering right now. Last checked 8 min ago. It exposes 1 tools. Last commit 13 Sep 2026.

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

Uptime history 64 days of history · worst day 99%

64 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

366 ms

Response time

average over 24h

Stars

last commit 13 Sep 2026

Nothing serious here today

Today is the operative word: we check POSTFACT — Resolve Ambiguous Side Effects Before Retry every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.postfact]
url = "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

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

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

resolve

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.

Endpoints

URL	Transport	State	Latency	Checked
https://postfact-api-production.up.railway.app/mcp	streamable-http	answering	364 ms	8 min ago

Alternatives to POSTFACT — Resolve Ambiguous Side Effects Before Retry

same job, measured the same way

Merchant Context

by ihint

Resolve sourced merchant facts and safe actions before an agent acts.

9 tools answering

Safeprompt

by safeprompt

Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM.

18 installs/wk local only

Veritap

by veritap

Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.

53 installs/wk 6 tools answering

once

by aurumflux20

Run a side effect exactly once under retries, redelivery, and concurrent workers.

92 installs/wk local only

MCP Bluesky Brand Presence Mapper

by mambabuilt

Resolve a company domain to its Bluesky account with exact follower, following and post counts.

108 installs/wk local only

factstore

by victor-eu

A fact store for AI agents, on Postgres: registered attributes, every write citing its evidence.

72 installs/wk local only

Tewip

by hmamut39

Proves software work: triages failing tests, checks whether a test can fail, and reads migrations.

4 389 installs/wk local only

Units-LE

by nolindnaidoo

Extract durations, sizes, percentages and frequencies in one base unit, refusing ambiguous ones.

252 installs/wk local only

POSTFACT — Resolve Ambiguous Side Effects Before Retry — questions

Answers built from our own checks of this server.

What can POSTFACT — Resolve Ambiguous Side Effects Before Retry do?

It exposes 1 tools, read directly from the server on our last check. Among them: resolve_outcome. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is POSTFACT — Resolve Ambiguous Side Effects Before Retry working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 366 ms. The bar chart above shows every period we have measured.

How do I connect POSTFACT — Resolve Ambiguous Side Effects Before Retry?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does POSTFACT — Resolve Ambiguous Side Effects Before Retry need an API key?

No. POSTFACT — Resolve Ambiguous Side Effects Before Retry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is POSTFACT — Resolve Ambiguous Side Effects Before Retry?

It answers our handshake in 366 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is POSTFACT — Resolve Ambiguous Side Effects Before Retry open source?

We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.