POSTFACT — Resolve Ambiguous Side Effects Before Retry
REMOTE · POSTFACT-API-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 23
Resolve whether an uncertain side-effecting action completed before software retries it.
Available components
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 →
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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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'
{
"mcpServers": {
"gsterlingpress-postfact": {
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
} {
"servers": {
"gsterlingpress-postfact": {
"type": "http",
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
} [mcp_servers.gsterlingpress-postfact] url = "https://postfact-api-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gsterlingpress-postfact": {
"type": "remote",
"url": "https://postfact-api-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add gsterlingpress-postfact --url 'https://postfact-api-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
gsterlingpress-postfact:
url: "https://postfact-api-production.up.railway.app/mcp" {
"McpServers": {
"gsterlingpress-postfact": {
"Transport": "http",
"Url": "https://postfact-api-production.up.railway.app/mcp"
}
}
} assistant mcp add gsterlingpress-postfact -t streamable-http -u 'https://postfact-api-production.up.railway.app/mcp'
{
"mcpServers": {
"gsterlingpress-postfact": {
"type": "http",
"url": "https://postfact-api-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 66
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 23 Aug 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=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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 |
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.
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.
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 71 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 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.