Safeagent

io.github.azender1Published by GitHub account azender1v0.1.22Updated Oct 27, 2026

Exactly-once execution guard for AI agents. Prevents duplicate payments and webhooks on retry.

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.azender1/safeagent
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account azender1 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.azender1%2Fsafeagent.svg)](https://sourceweft.com/mcp/io.github.azender1%2Fsafeagent?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local Python execution guard that lets an assistant claim, settle and audit stable request IDs so retried actions are not run twice.

What you can do: Claim an action under a stable request_id, receiving PROCEED on the first call and SKIP on repeats
Settle a claim after the action fires, moving it from PENDING to COMMITTED with a stored result
Query claim history filtered by agent, action, status or time range
Use a free test claim endpoint limited to 10 calls per IP
Run the same claim logic locally against an embedded SQLite table instead of the hosted API
When to use it: Useful when an agent retries side-effecting steps such as payments, emails, webhooks, orders or provisioning and duplicates would be costly. It suits developers who want a durable claim record before and after an external call, or a local SQLite guard pattern inside a Python agent.
Requirements: Runs as a local Python package (pip install safeagent-exec-guard) over stdio. The hosted API is reached over the network at a public endpoint; no API key, header or environment variable is declared. The README also shows an embedded SQLite variant that needs no network call.

Before you install

The README states the guarantee covers local claim state only, not the external outcome: PENDING means unresolved, and end-to-end exactly-once effects still need provider-native idempotency or reconciliation. Request IDs and action metadata are sent to a third-party hosted service, and completed actions are anchored to an external ledger. The free test endpoint is capped at 10 calls per IP.

Installation

In SourceWeft

Open Safeagent in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SafeAgent — Execution Guard for AI Agents

[Mycelium Provider]

POST /claim · safeagent-production.up.railway.app
Dashboard: safeagent-dashboard-2.vercel.app

bash

# Claim an action — free, no payment header requiredcurl -s -X POST https://safeagent-production.up.railway.app/claim \  -H "Content-Type: application/json" \  -d '{"request_id":"order:TQQQ:buy:6:2026-05-19T13:31:00-04:00","action":"order"}'# → {"status":"PROCEED","request_id":"..."}
# Settle after the action firescurl -s -X POST https://safeagent-production.up.railway.app/settle/order:TQQQ:buy:6:2026-05-19T13:31:00-04:00 \  -H "Content-Type: application/json" \  -d '{"result":{"status":"completed"}}'# → {"status":"committed","request_id":"..."}
# Retry with the same request_id — returns SKIPcurl -s -X POST https://safeagent-production.up.railway.app/claim \  -H "Content-Type: application/json" \  -d '{"request_id":"order:TQQQ:buy:6:2026-05-19T13:31:00-04:00","action":"order"}'# → {"status":"SKIP","request_id":"...","existing":{...}}
# Free test endpoint — same logic, limited to 10 calls per IPcurl -s -X POST https://safeagent-production.up.railway.app/claim/test \  -H "Content-Type: application/json" \  -d '{"agent_id":"bot-1","action_type":"order","scope":"TQQQ:buy:bar:2026-05-19T13:31:00-04:00"}'# → {"status":"PROCEED","request_id":"...","test":true,"calls_remaining":9}

# Claim an action — free, no payment header requiredcurl -s -X POST https://safeagent-production.up.railway.app/claim \  -H "Content-Type: application/json" \  -d '{"request_id":"order:TQQQ:buy:6:2026-05-19T13:31:00-04:00","action":"order"}'# → {"status":"PROCEED","request_id":"..."}
# Settle after the action firescurl -s -X POST https://safeagent-production.up.railway.app/settle/order:TQQQ:buy:6:2026-05-19T13:31:00-04:00 \  -H "Content-Type: application/json" \  -d '{"result":{"status":"completed"}}'# → {"status":"committed","request_id":"..."}
# Retry with the same request_id — returns SKIPcurl -s -X POST https://safeagent-production.up.railway.app/claim \  -H "Content-Type: application/json" \  -d '{"request_id":"order:TQQQ:buy:6:2026-05-19T13:31:00-04:00","action":"order"}'# → {"status":"SKIP","request_id":"...","existing":{...}}
# Free test endpoint — same logic, limited to 10 calls per IPcurl -s -X POST https://safeagent-production.up.railway.app/claim/test \  -H "Content-Type: application/json" \  -d '{"agent_id":"bot-1","action_type":"order","scope":"TQQQ:buy:bar:2026-05-19T13:31:00-04:00"}'# → {"status":"PROCEED","request_id":"...","test":true,"calls_remaining":9}

Indexed on Bazaar.

Measured CrewAI retry A/B

A credential-free experiment exercises CrewAI 1.15.21's actual same-process `ToolUsage._use` retry against SafeAgent 0.1.23. Across 30 post-effect/pre-confirmation trials, the unguarded path recorded two effects per logical action; the SafeAgent path recorded one effect and retained a `PENDING` claim for reconciliation.

Scope: scripted deterministic LLM and harmless effect recorded through an out-of-process capability-separated ledger. This does not validate process death, fresh-worker recovery, a real external provider, or SafeAgent Control reconciliation.

Method, source, tests, hashes, and 180-trial evidence

SafeAgent Control founding pilots

Two bounded, read-only reconciliation pilots are open for outside operators. There is no fee unless SafeAgent Control identifies a previously unknown, reproducible discrepancy that the operator agrees is actionable.

Scope and outcome-based terms

Mycelium Trails

This implementation is a Mycelium Provider. Each completed action submits a trail to ARGENTUM with a content-addressed action_ref (JCS+SHA-256 over the four preimage fields). The returned mycelium_trail_id is included in every receipt for independent verification.

Verified on Soma

SafeAgent is the first verified external integrator on Soma — the Mycelium agent catalog. Every production execution is anchored on-chain via Mycelium Trails and independently verifiable without going through the operator.

Integrator badge — verified external client running Mycelium Trails in production
Live trails — https://argentum-api.rgiskard.xyz/dashboard/trails?client=safeagent-prod
Public audit — any auditor can verify SafeAgent executions independently

What it does

SafeAgent is a durable execution-claim guard. It suppresses concurrent and repeated attempts that use the same stable request_id, and preserves unresolved attempts for reconciliation instead of silently retrying them.

Every action gets a stable request_id derived from the logical action. A new key returns PROCEED; a settled key returns SKIP with its stored result. A key left PENDING after a timeout or crash remains blocked because local state alone cannot prove whether the provider accepted the action. Recover it only after checking provider evidence or using provider-native idempotency.

State machine: CLAIMABLE → PENDING → COMMITTED; later claims observe PENDING or SKIP.

Common failure modes SafeAgent prevents:

Scenario	Without SafeAgent	With SafeAgent
Stripe charge times out after acceptance	Retry may charge twice	Same key remains PENDING until provider reconciliation
Welcome email on signup retried	User gets two welcome emails	Second send returns SKIP
Webhook delivered twice (Stripe/GitHub/Twilio guarantee at-least-once)	Event processed twice	Second processing returns SKIP
Workspace provisioned on retry	Two workspaces created	Second provision returns SKIP
AI agent tool call retried after crash	Duplicate side effect	Same key stays blocked; outcome is explicitly unresolved

Guarantee boundary: SafeAgent proves local claim state, not the external outcome. COMMITTED means the caller settled a receipt. PENDING means unresolved—not failed and not confirmed successful. End-to-end exactly-once effects require provider-native idempotency and/or reconciliation with the provider's authoritative records.

The stack

SafeAgent is the durable claim and duplicate-suppression layer in an agent execution integrity stack:

Polaris (commit-gated authorization)└── AgentGraph safety verdict (pre-execution safety gate)    └── SafeAgent (durable claim guard)  ← you are here        └── Mycelium Trails (on-chain anchor)

Polaris (commit-gated authorization)└── AgentGraph safety verdict (pre-execution safety gate)    └── SafeAgent (durable claim guard)  ← you are here        └── Mycelium Trails (on-chain anchor)

Each layer is independently authored and independently verifiable. None trusts the others.

API

POST /claim

Gate an action. Returns PROCEED on first call, SKIP on any repeat.

Request body:

request_id — stable identifier derived from what the agent is doing. Same inputs = same key.
action — the action type being gated (e.g. payment.send, email, trade, order)

Response:

Retry with the same payload:

json

{ "status": "SKIP", "request_id": "order:TQQQ:buy:6:2026-05-19T13:31:00-04:00", "existing": {...} }

{ "status": "SKIP", "request_id": "order:TQQQ:buy:6:2026-05-19T13:31:00-04:00", "existing": {...} }

POST /settle/{request_id}

Settle a claim after the action fires. Advances status from PENDING to COMMITTED.

bash

curl -s -X POST https://safeagent-production.up.railway.app/settle/order:TQQQ:buy:6:2026-05-19T13:31:00-04:00 \  -H "Content-Type: application/json" \  -d '{"result":{"status":"completed","txid":"abc123"}}'

curl -s -X POST https://safeagent-production.up.railway.app/settle/order:TQQQ:buy:6:2026-05-19T13:31:00-04:00 \  -H "Content-Type: application/json" \  -d '{"result":{"status":"completed","txid":"abc123"}}'

POST /claim/test

Free test endpoint — same logic, no payment required. Limited to 10 calls per IP total.

bash

curl -s -X POST https://safeagent-production.up.railway.app/claim/test \  -H "Content-Type: application/json" \  -d '{"agent_id":"bot-1","action_type":"order","scope":"TQQQ:buy:6:bar:2026-05-19T13:31:00-04:00"}'

curl -s -X POST https://safeagent-production.up.railway.app/claim/test \  -H "Content-Type: application/json" \  -d '{"agent_id":"bot-1","action_type":"order","scope":"TQQQ:buy:6:bar:2026-05-19T13:31:00-04:00"}'

GET /audit

Full claim history. Filter by agent_id, action, status, or timestamp range.

Parameters: agent_id, action, status, from_ts, to_ts, limit (max 1000), offset.

Integration

Python

python

import requests
def claim(request_id: str, action: str) -> dict:    r = requests.post(        "https://safeagent-production.up.railway.app/claim",        headers={"Content-Type": "application/json"},        json={"request_id": request_id, "action": action}    )    return r.json()  # {"status": "PROCEED"|"SKIP", "request_id": "..."}
def settle(request_id: str, result: dict) -> dict:    r = requests.post(        f"https://safeagent-production.up.railway.app/settle/{request_id}",        headers={"Content-Type": "application/json"},        json={"result": result}    )    return r.json()
# Usageresponse = claim("payment:customer-123:invoice-456", "payment.send")if response["status"] == "PROCEED":    result = send_payment(...)    settle("payment:customer-123:invoice-456", {"status": "completed"})elif response["status"] == "SKIP":    print("Already executed, skipping")

import requests
def claim(request_id: str, action: str) -> dict:    r = requests.post(        "https://safeagent-production.up.railway.app/claim",        headers={"Content-Type": "application/json"},        json={"request_id": request_id, "action": action}    )    return r.json()  # {"status": "PROCEED"|"SKIP", "request_id": "..."}
def settle(request_id: str, result: dict) -> dict:    r = requests.post(        f"https://safeagent-production.up.railway.app/settle/{request_id}",        headers={"Content-Type": "application/json"},        json={"result": result}    )    return r.json()
# Usageresponse = claim("payment:customer-123:invoice-456", "payment.send")if response["status"] == "PROCEED":    result = send_payment(...)    settle("payment:customer-123:invoice-456", {"status": "completed"})elif response["status"] == "SKIP":    print("Already executed, skipping")

SaaS (Stripe / email / webhooks)

For production Stripe PaymentIntents, use the permit-gated adapter documented in SafeAgent Boundary. It keeps the Stripe credential outside the agent, passes the consumed permit ID to Stripe as the native idempotency key, persists the provider correlation, verifies webhook signatures and supports authoritative read-back. The simple claim/settle snippet below illustrates the generic API only; it is not the provider adapter.

Run the bounded test-mode example in examples/stripe_payment_intent_guard.py. The verification record documents the observed end-to-end result: one successful Stripe sandbox PaymentIntent, an exact replay blocked before provider dispatch, and authoritative reconciliation by retrieve.

python

import requests
def safe_stripe_charge(customer_id, amount, idempotency_key):    request_id = f"stripe:charge:{customer_id}:{idempotency_key}"
    response = requests.post(        "https://safeagent-production.up.railway.app/claim",        headers={"Content-Type": "application/json"},        json={"request_id": request_id, "action": "stripe_charge"}    ).json()
    if response["status"] == "SKIP":        return response.get("existing")
    charge = stripe.PaymentIntent.create(        amount=amount,        currency="usd",        customer=customer_id,        idempotency_key=request_id,    )    requests.post(        f"https://safeagent-production.up.railway.app/settle/{request_id}",        headers={"Content-Type": "application/json"},        json={"result": {"charge_id": charge.id}}    )    return charge

import requests
def safe_stripe_charge(customer_id, amount, idempotency_key):    request_id = f"stripe:charge:{customer_id}:{idempotency_key}"
    response = requests.post(        "https://safeagent-production.up.railway.app/claim",        headers={"Content-Type": "application/json"},        json={"request_id": request_id, "action": "stripe_charge"}    ).json()
    if response["status"] == "SKIP":        return response.get("existing")
    charge = stripe.PaymentIntent.create(        amount=amount,        currency="usd",        customer=customer_id,        idempotency_key=request_id,    )    requests.post(        f"https://safeagent-production.up.railway.app/settle/{request_id}",        headers={"Content-Type": "application/json"},        json={"result": {"charge_id": charge.id}}    )    return charge

Webhook deduplication — stable event IDs suppress repeated processing after a settled result; unresolved PENDING events stay blocked for investigation:

python

def handle_stripe_webhook(event):    response = requests.post(        "https://safeagent-production.up.railway.app/claim",        headers={"Content-Type": "application/json"},        json={"request_id": event["id"], "action": "stripe_event"}    ).json()
    if response["status"] == "SKIP":        return {"ok": True}
    provision_subscription(event)    requests.post(        f"https://safeagent-production.up.railway.app/settle/{event['id']}",        headers={"Content-Type": "application/json"},        json={"result": {"processed": True}}    )

def handle_stripe_webhook(event):    response = requests.post(        "https://safeagent-production.up.railway.app/claim",        headers={"Content-Type": "application/json"},        json={"request_id": event["id"], "action": "stripe_event"}    ).json()
    if response["status"] == "SKIP":        return {"ok": True}
    provision_subscription(event)    requests.post(        f"https://safeagent-production.up.railway.app/settle/{event['id']}",        headers={"Content-Type": "application/json"},        json={"result": {"processed": True}}    )

CrewAI

python

from crewai import Agentimport sqlite3
guard_con = sqlite3.connect("safeagent_orders.db", check_same_thread=False)# ... same guard pattern, keyed on tool_name + input hash + session_id

from crewai import Agentimport sqlite3
guard_con = sqlite3.connect("safeagent_orders.db", check_same_thread=False)# ... same guard pattern, keyed on tool_name + input hash + session_id

PR crewAIInc/crewAI#5822 adds pluggable idempotency backends. SafeAgent's SQLite schema is compatible.

WisePick

WisePick is a deterministic routing layer for agent runtimes. The integration splits capability selection from durable, idempotent execution — WisePick answers what and which provider, SafeAgent answers whether this logical work already ran.

Stack:

Adapter: adapters/safeagent_adapter.py
Integration docs: docs/integrations/safeagent.md
Integration thread: SafeAgent #9

Local guard (embedded SQLite)

The same durable claim behavior without the network call. Drop this into any Python agent:

python

import jsonimport sqlite3
_SA_DB = "safeagent_orders.db"_sa_con = sqlite3.connect(_SA_DB, check_same_thread=False)_sa_con.execute("""CREATE TABLE IF NOT EXISTS orders (    request_id TEXT PRIMARY KEY,    result     TEXT,    status     TEXT DEFAULT 'PENDING',    created_at TEXT DEFAULT (datetime('now')))""")_sa_con.commit()
def place_order_with_guard(symbol, qty, side, bar_ts):    request_id = f"order:{symbol}:{side}:{qty}:{bar_ts}"
    cur = _sa_con.execute(        "INSERT OR IGNORE INTO orders (request_id, status) VALUES (?, 'PENDING')",        (request_id,)    )    _sa_con.commit()
    if cur.rowcount == 0:        row = _sa_con.execute(            "SELECT status, result FROM orders WHERE request_id = ?",            (request_id,)        ).fetchone()        if row and row[0] == 'COMMITTED':            print(f"SAFEAGENT SKIP: {request_id}")            return row[1]        raise RuntimeError(            f"SAFEAGENT BLOCKED: unresolved PENDING claim for {request_id}"        )
    result = place_order(symbol, qty, side)
    _sa_con.execute(        "UPDATE orders SET status='COMMITTED', result=? WHERE request_id=?",        (json.dumps(str(result)), request_id)    )    _sa_con.commit()    return result

import jsonimport sqlite3
_SA_DB = "safeagent_orders.db"_sa_con = sqlite3.connect(_SA_DB, check_same_thread=False)_sa_con.execute("""CREATE TABLE IF NOT EXISTS orders (    request_id TEXT PRIMARY KEY,    result     TEXT,    status     TEXT DEFAULT 'PENDING',    created_at TEXT DEFAULT (datetime('now')))""")_sa_con.commit()
def place_order_with_guard(symbol, qty, side, bar_ts):    request_id = f"order:{symbol}:{side}:{qty}:{bar_ts}"
    cur = _sa_con.execute(        "INSERT OR IGNORE INTO orders (request_id, status) VALUES (?, 'PENDING')",        (request_id,)    )    _sa_con.commit()
    if cur.rowcount == 0:        row = _sa_con.execute(            "SELECT status, result FROM orders WHERE request_id = ?",            (request_id,)        ).fetchone()        if row and row[0] == 'COMMITTED':            print(f"SAFEAGENT SKIP: {request_id}")            return row[1]        raise RuntimeError(            f"SAFEAGENT BLOCKED: unresolved PENDING claim for {request_id}"        )
    result = place_order(symbol, qty, side)
    _sa_con.execute(        "UPDATE orders SET status='COMMITTED', result=? WHERE request_id=?",        (json.dumps(str(result)), request_id)    )    _sa_con.commit()    return result

Case study: crash-retry duplicate prevention

A trading bot fires a market order to buy 6 shares of TQQQ. The broker accepts it. The bot crashes before updating state. On restart — same signal, same bar — the bot fires again. The broker fills it twice. The agent now holds 12 shares when it intended to hold 6.

This is not theoretical. It happens on any unhandled exception between order submission and state persistence.

SafeAgent derives a stable key before touching the broker:

First call: PROCEED. Side effect fires. Settle writes COMMITTED.
Crash and retry: SKIP. Broker never touched again.

Case study: live duplicate blocking — May 21, 2026

Six confirmed SKIP events from a live session on the full stack: DashClaw, SafeAgent, Mycelium Trails, Base/Arbitrum, broker Alpaca.

0942 ET: duplicate buy TQQQ qty=6 blocked, $452
0947 ET: duplicate add TQQQ qty=6 blocked, $452
0949 ET: duplicate sell TQQQ qty=12 on flip, $902
1000 ET: duplicate entry TQQQ qty=6 blocked, $454
1014 ET: duplicate sell TQQQ qty=18 on V20 flip, $1,350
1106 ET: duplicate SQQQ add during scale-in, $43

Full session data: https://gist.github.com/azender1/b9112b6519c935df4a75cb05cd250e26

Conformance

SafeAgent participates in the A2A cross-implementation conformance corpus. Byte-verified fixtures across four independent implementations:

kenneives (agentgraph) — verifier-attestation-v0: 30/30 ✓
evidai (LemonCake) — gated-preflight-v1: 33/33 ✓
haroldmalikfrimpong-ops (agentid) — independent verifier ✓
SafeAgent — claim-lifecycle conformance v1.1 ✓

A2A #1920 closed. All four implementations satisfy freshness and replay requirements.

Canonical `action_ref` derivation

JCS (RFC 8785), aligned with argentum-core, Nobulex, and APS:

python

import hashlibimport rfc8785
def compute_action_ref(    agent_id: str,    action_type: str,    scope: str,    timestamp: str,  # RFC 3339 UTC, 3-digit ms: "2026-05-15T10:00:00.123Z") -> str:    payload = {        "agent_id": agent_id,        "action_type": action_type,        "scope": scope,        "timestamp": timestamp,    }    canonical = rfc8785.dumps(payload)    return hashlib.sha256(canonical).hexdigest()

import hashlibimport rfc8785
def compute_action_ref(    agent_id: str,    action_type: str,    scope: str,    timestamp: str,  # RFC 3339 UTC, 3-digit ms: "2026-05-15T10:00:00.123Z") -> str:    payload = {        "agent_id": agent_id,        "action_type": action_type,        "scope": scope,        "timestamp": timestamp,    }    canonical = rfc8785.dumps(payload)    return hashlib.sha256(canonical).hexdigest()

timestamp is an RFC 3339 UTC string with exactly 3 millisecond digits. The trailing Z is mandatory.

Conformance fixtures: giskard09/argentum-core tag action-ref-v1.0

Deployment

Railway · Serverless OFF · always-on
PyPI: pip install safeagent-exec-guard
npm: npm install n8n-nodes-safeagent
MCP Registry: io.github.azender1/safeagent
Dashboard: safeagent-dashboard-2.vercel.app

License

Apache-2.0

Source: README.md at commit 2dfd694

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.22LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Safeagent

Overview

Installation

In SourceWeft

Other MCP clients

README

SafeAgent — Execution Guard for AI Agents

Measured CrewAI retry A/B

SafeAgent Control founding pilots

Mycelium Trails

Verified on Soma

What it does

The stack

API

POST /claim

POST /settle/{request_id}

POST /claim/test

GET /audit

Integration

Python

SaaS (Stripe / email / webhooks)

CrewAI

WisePick

Local guard (embedded SQLite)

Case study: crash-retry duplicate prevention

Case study: live duplicate blocking — May 21, 2026

Conformance

Canonical action_ref derivation

Deployment

License

Tools

Version history

Score

Canonical `action_ref` derivation