# 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.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-23

## Components

- remote · `postfact-api-production.up.railway.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/gsterlingpress-postfact/postfact-api-production.md), [page](https://verifymcp.io/servers/gsterlingpress-postfact/postfact-api-production)

## Channel facts

- Endpoint: `https://postfact-api-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 156 tokens (~156/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "gsterlingpress-postfact": {
      "type": "http",
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.gsterlingpress-postfact]
url = "https://postfact-api-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gsterlingpress-postfact": {
      "type": "remote",
      "url": "https://postfact-api-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gsterlingpress-postfact --url 'https://postfact-api-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gsterlingpress-postfact:
    url: "https://postfact-api-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "gsterlingpress-postfact": {
      "Transport": "http",
      "Url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add gsterlingpress-postfact -t streamable-http -u 'https://postfact-api-production.up.railway.app/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-23 (score 71, +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.

### 2026-08-21 (score 70, +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.

### 2026-08-19 (score 69, +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.

### 2026-08-17 (score 68, +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.

### 2026-08-15 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-14 (score 66)

First indexed and scored.

## MCP tools (1)

### `resolve_outcome` (~125 tokens)

Resolve Ambiguous Side Effect

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.

Input parameters:

- `evidence` (object)
- `failure` (string)
- `idempotencyKey` (string)
- `method` (string)
- `requestId` (string)
- `resourceRef` (string)
- `sideEffect` (boolean)
- `status` (integer)
- `transactionRef` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gsterlingpress-postfact/postfact-api-production#diagnostics

## Score history

- 2026-08-23: 71
- 2026-08-22: 70
- 2026-08-21: 70
- 2026-08-20: 69
- 2026-08-19: 69
- 2026-08-18: 68
- 2026-08-17: 68
- 2026-08-16: 67
- 2026-08-15: 67
- 2026-08-14: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://postfact-api-production.up.railway.app/mcp
- Repository: https://github.com/GSterlingPress/postfact-api
- Website: https://postfact-api-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/gsterlingpress-postfact/postfact-api-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/gsterlingpress-postfact/postfact-api-production.json
- HTML version of this page: https://verifymcp.io/servers/gsterlingpress-postfact/postfact-api-production