POSTFACT — Resolve Ambiguous Side Effects Before Retry
REMOTE · POSTFACT-API-PRODUCTION.UP.RAILWAY.APP
Resolve whether an uncertain side-effecting action completed before software retries it.
Available components
Last scanned (15 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 156 tokens (~156/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://postfact-api-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of postfact-api-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://postfact-api-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://postfact-api-production.up.railway.app/mcp | HTTPS enforced | 301 | https://postfact-api-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
resolve_outcome Resolve Ambiguous Side Effect ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | object | – | – |
| failure | string | – | – |
| idempotencyKey | string | – | – |
| method | string | – | – |
| requestId | string | – | – |
| resourceRef | string | – | – |
| sideEffect | boolean | – | – |
| status | integer | – | – |
| transactionRef | string | – | – |
No output schema declared.
No examples provided.
How do I install the POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server?
POSTFACT — Resolve Ambiguous Side Effects Before Retry is a hosted endpoint at https://postfact-api-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · postfact-api-production.up.railway.app
claude mcp add --transport http gsterlingpress-postfact 'https://postfact-api-production.up.railway.app/mcp'
What is the POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server?
POSTFACT — Resolve Ambiguous Side Effects Before Retry is an MCP server listed in the public MCP registry as io.github.GSterlingPress/postfact. Resolve whether an uncertain side-effecting action completed before software retries it. This page covers its hosted endpoint (https://postfact-api-production.up.railway.app/mcp).
Is the POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server safe to use?
POSTFACT — Resolve Ambiguous Side Effects Before Retry scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server expose?
POSTFACT — Resolve Ambiguous Side Effects Before Retry exposes 1 tool: resolve_outcome. Their descriptions and schemas cost roughly 125 tokens of context every time the server is loaded.
Does the POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server require authentication?
No. We connected to POSTFACT — Resolve Ambiguous Side Effects Before Retry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server still maintained?
POSTFACT — Resolve Ambiguous Side Effects Before Retry is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.