Index / MCP servers / POSTFACT — Resolve Ambiguous Side Effects Before Retry

POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server

POSTFACT — Resolve Ambiguous Side Effects Before Retry is an MCP server with 1 tool an agent can call, among them resolve_outcome. It answers at https://postfact-api-production.up.railway.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 19 October 2026, succeeded.

Status
Answering
Tools
1
Reliability
6 of 6 checks
Response time
285 ms
Transport
streamable HTTP
Last checked
19 October 2026

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

Description as the publisher wrote it.

The 1 tool POSTFACT — Resolve Ambiguous Side Effects Before Retry offers

ToolWhat it does
resolve_outcomeCall 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 saf
Inputs: method, status, failure, sideEffect, idempotencyKey, requestId

Add POSTFACT — Resolve Ambiguous Side Effects Before Retry to your AI client

Every block below points at https://postfact-api-production.up.railway.app/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http postfact-resolve-ambiguous-side https://postfact-api-production.up.railway.app/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://postfact-api-production.up.railway.app/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "postfact-resolve-ambiguous-side": {
      "type": "http",
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "postfact-resolve-ambiguous-side": {
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "serverUrl": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: POSTFACT — Resolve Ambiguous Side Effects Before Retry
version: 0.0.1
schema: v1
mcpServers:
  - name: POSTFACT — Resolve Ambiguous Side Effects Before Retry
    type: streamable-http
    url: https://postfact-api-production.up.railway.app/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "httpUrl": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "type": "http",
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "postfact-resolve-ambiguous-side": {
      "url": "https://postfact-api-production.up.railway.app/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fpostfact-api-production.up.railway.app%2Fmcp&type=streamable_http&id=postfact-resolve-ambiguous-side&name=POSTFACT%20%E2%80%94%20Resolve%20Ambiguous%20Side%20Effects%20Before%20Retry

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

It answered our last check on 19 October 2026 in 285 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to POSTFACT — Resolve Ambiguous Side Effects Before Retry

Questions about POSTFACT — Resolve Ambiguous Side Effects Before Retry

How many tools does POSTFACT — Resolve Ambiguous Side Effects Before Retry have?

1, as returned by the server's own tools/list on 12 September 2026: resolve_outcome.

Is POSTFACT — Resolve Ambiguous Side Effects Before Retry down?

It answered our last check on 19 October 2026 in 285 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add POSTFACT — Resolve Ambiguous Side Effects Before Retry to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://postfact-api-production.up.railway.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

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

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.gsterlingpress. Endpoint host: postfact-api-production.up.railway.app. ARD identifier: urn:air:io.github.gsterlingpress:mcp:postfact. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.