Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ONCE — Exactly-Once Reliability for AI Agent Actions

REMOTE · OPTIMISTIC-COMPASSION-PRODUCTION.UP.RAILWAY.APP

Prevent duplicate AI-agent side effects with idempotency, verification, and durable receipts.

0 this week 76 Trust /100

Last scanned (18 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 272 tokens (~136/item across 2 items; 2 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 Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "once_execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 3 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 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
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Probed https://optimistic-compassion-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 optimistic-compassion-production.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
railway.app. No DS 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
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://optimistic-compassion-production.up.railway.app/mcp Verified 200
http (plaintext) http://optimistic-compassion-production.up.railway.app/mcp HTTPS enforced 301 https://optimistic-compassion-production.up.railway.app/mcp
MCP tools · 2 exposed · ~191 tokens

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 →

Tool Tokens
once_demo ~77

SAFE ZERO-SETUP DEMO. Call this tool twice with the same id to see ONCE suppress the second execution. Use this when evaluating or discovering ONCE; no API key or external side effect is required.

NameTypeReqDescription
idstringyesAny stable demo id. Reuse the SAME id on the second call to prove duplicate suppression.

No output schema declared.

No examples provided.

once_execute ~114

CALL THIS when an AI agent is about to perform or retry a consequential external side effect where duplication would be harmful: purchase, refund, payment, booking, send, create, modify, submit, or delete. ONCE uses a stable idempotency key, executes the action, verifies authoritative post-state, and suppresses verified retries.

NameTypeReqDescription
actionobjectyes–
idempotencyKeystringyesStable key representing this one intended real-world action. Reuse it for retries.
verifyobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the ONCE — Exactly-Once Reliability for AI Agent Actions MCP server?

ONCE — Exactly-Once Reliability for AI Agent Actions is a hosted endpoint at https://optimistic-compassion-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 · optimistic-compassion-production.up.railway.app

# add to Claude Code
claude mcp add --transport http gsterlingpress-once 'https://optimistic-compassion-production.up.railway.app/mcp'
Common questions

What is the ONCE — Exactly-Once Reliability for AI Agent Actions MCP server?

ONCE — Exactly-Once Reliability for AI Agent Actions is an MCP server listed in the public MCP registry as io.github.GSterlingPress/once. Prevent duplicate AI-agent side effects with idempotency, verification, and durable receipts. This page covers its hosted endpoint (https://optimistic-compassion-production.up.railway.app/mcp).

Is the ONCE — Exactly-Once Reliability for AI Agent Actions MCP server safe to use?

ONCE — Exactly-Once Reliability for AI Agent Actions scores 76 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 ONCE — Exactly-Once Reliability for AI Agent Actions MCP server expose?

ONCE — Exactly-Once Reliability for AI Agent Actions exposes 2 tools: once_demo, once_execute. Their descriptions and schemas cost roughly 191 tokens of context every time the server is loaded.

Does the ONCE — Exactly-Once Reliability for AI Agent Actions MCP server require authentication?

No. We connected to ONCE — Exactly-Once Reliability for AI Agent Actions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ONCE — Exactly-Once Reliability for AI Agent Actions MCP server still maintained?

ONCE — Exactly-Once Reliability for AI Agent Actions is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ONCE — Exactly-Once Reliability for AI Agent Actions MCP server?

VerifyMCP ran 12 checks on ONCE — Exactly-Once Reliability for AI Agent Actions, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ONCE — Exactly-Once Reliability for AI Agent Actions: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.