Ext Ops Panel
Open dashboard
Comparison

ONCE — Exactly-Once Reliability for AI Agent Actions vs io.github.imran-siddique/agentos

ONCE — Exactly-Once Reliability for AI Agent Actions is an MCP server published by GSterlingPress. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.imran-siddique/agentos is an MCP server published by imran-siddique. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceONCE — Exactly-Once Reliability for AI Agent Actionsio.github.imran-siddique/agentos
Official MCP Registry Listed
Version: 0.8.4
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (npm): 193
Downloads/week (npm): 22
Forks (GitHub): 26
Stars (GitHub): 74
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ONCE — Exactly-Once Reliability for AI Agent Actions vs io.github.imran-siddique/agentos
FactONCE — Exactly-Once Reliability for AI Agent Actionsio.github.imran-siddique/agentos
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)74 (better)
Forks (GitHub) (differs)0 (worse)26 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (optimistic-compassion-production.up.railway.app/mcp)On your machine (agentos-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/gsterlingpress/once-apigithub.com/imran-siddique/agent-os
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

ONCE — Exactly-Once Reliability for AI Agent Actions

In its own words, on Official MCP Registry:

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

io.github.imran-siddique/agentos

In its own words, on Official MCP Registry:

Build and manage policy-compliant AI agents with safety enforcement and compliance checking

How to run each

ONCE — Exactly-Once Reliability for AI Agent Actions As a remote MCP server

Claude Code
claude mcp add --transport http once https://optimistic-compassion-production.up.railway.app/mcp

io.github.imran-siddique/agentos As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agentos -- npx -y agentos-mcp-server

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ONCE — Exactly-Once Reliability for AI Agent Actions has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of ONCE — Exactly-Once Reliability for AI Agent Actions publish no settings it asks for, so we do not compare settings.

What it can do: ONCE — Exactly-Once Reliability for AI Agent Actions · What it can do: io.github.imran-siddique/agentos · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built