Remote MCP · Endpoint

POSTFACT — Resolve Ambiguous Side Effects Before Retry MCP server

No. POSTFACT — Resolve Ambiguous Side Effects Before Retry answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.GSterlingPress/postfact
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
116 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Resolve whether an uncertain side-effecting action completed before software retries it.
Website
https://postfact-api-production.up.railway.app/
Repository
https://github.com/GSterlingPress/postfact-api
Listing
From the official MCP registry (active).
Recent checks of POSTFACT — Resolve Ambiguous Side Effects Before Retry
CheckedResultHandshake
2 hours agoHandshake completed116 ms
1 day agoHandshake completed109 ms
3 days agoHandshake completed110 ms
3 days agoHandshake completed106 ms
4 days agoHandshake completed149 ms
5 days agoHandshake completed107 ms
7 days agoHandshake completed128 ms
10 days agoHandshake completed124 ms
12 days agoHandshake completed167 ms
15 days agoHandshake completed107 ms
17 days agoHandshake completed317 ms
19 days agoHandshake completed106 ms
21 days agoHandshake completed109 ms
23 days agoHandshake completed120 ms
25 days agoHandshake completed119 ms
26 days agoHandshake completed111 ms
28 days agoHandshake completed108 ms
29 days agoHandshake completed103 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with POSTFACT — Resolve Ambiguous Side Effects Before Retry and makes no claim about it beyond what these checks measured.