MCP.Market

POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server

online · 100% uptime
by GSterlingPress·io.github.GSterlingPress/postfact·v0.1.1
No reviews yet

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

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed POSTFACT — Resolve Ambiguous Side Effects Before Retry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

POSTFACT — Resolve Ambiguous Side Effects Before Retry tools (1)

write = sends, deletes, buys or posts
  • resolve_outcomeFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 267ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 20 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How POSTFACT — Resolve Ambiguous Side Effects Before Retry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
333 ms
faster than 44% of 30,031 servers

What its tools let an agent do: 1 read

Install POSTFACT — Resolve Ambiguous Side Effects Before Retry in Claude Code, Cursor or VS Code

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

What the publisher says

From the POSTFACT — Resolve Ambiguous Side Effects Before Retry repository's README, as published. We do not edit it. Read it on GitHub

POSTFACT

Did the call actually happen?

POSTFACT is a tiny ambiguous-outcome resolver for autonomous software. Use it after a side-effecting API/tool action fails ambiguously and before retrying.

Production: https://postfact-api-production.up.railway.app

It is intentionally strict:

  • DONE only when affirmative evidence establishes completion.
  • NOT_DONE only when affirmative evidence establishes non-execution.
  • UNKNOWN whenever evidence is insufficient. UNKNOWN is the safe default.

POSTFACT does not execute the underlying action, move money, or pretend a timeout means failure.

REST

Production endpoint: POST https://postfact-api-production.up.railway.app/v1/resolve

Input accepts method/status/failure, side-effect and idempotency context, durable references, and optional affirmative evidence. Output is state, retry_safe, confidence, evidence, and next.

MCP

Remote endpoint: POST https://postfact-api-production.up.railway.app/mcp

Tool: resolve_outcome

The tool description explicitly tells agents to invoke POSTFACT after an ambiguous side-effect failure and before retry.

Middleware-shaped contract

const outcome = await postfact.resolve(failureContext)
if (outcome.state === 'DONE') return completed
if (outcome.state === 'NOT_DONE' && outcome.retry_safe) return retry()
return verifyOrHold()

Future SDKs can wrap retry middleware without changing the wire contract.

POSTFACT + RECOVER

POSTFACT answers what can we establish happened? RECOVER answers what is the safest next action? A future retry stack can call POSTFACT first, then RECOVER when the outcome remains uncertain.

Safe discovery and demo

  • Health: GET https://postfact-api-production.up.railway.app/health
  • Demo: GET https://postfact-api-production.up.railway.app/demo
  • Activity: GET https://postfact-api-production.up.railway.app/activity
  • Machine-readable activity: GET https://postfact-api-production.up.railway.app/activity.json

GET /demo is deliberately excluded from real-use analytics.

Real-use scoreboard

GET /activity shows the permanent FIRST 10 TRUE STRANGERS scoreboard. GET /activity.json exposes its machine-readable summary. Demo/internal traffic is excluded. Production persistent storage is mounted at /data.

Run

npm test
npm start

Default port: 8080.

Nothing above is checked by us. What we check is on the safety report.

POSTFACT — Resolve Ambiguous Side Effects Before Retry: common questions

Is POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the POSTFACT — Resolve Ambiguous Side Effects Before Retry safety report
How do I install POSTFACT — Resolve Ambiguous Side Effects Before Retry?
It runs remotely at postfact-api-production.up.railway.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does POSTFACT — Resolve Ambiguous Side Effects Before Retry need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is POSTFACT — Resolve Ambiguous Side Effects Before Retry maintained?
The last commit was 52 days ago (2026-09-13). The latest release is v0.1.1.
Is POSTFACT — Resolve Ambiguous Side Effects Before Retry up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does POSTFACT — Resolve Ambiguous Side Effects Before Retry compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from GSterlingPress →