Deadlatch

Name: Deadlatch
Author: Diabloluo

by Diabloluoversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.Diabloluo/deadlatch

Install

Overview

Description from the maker (original English)

Local advisory pre-trade risk gate for agents. Never places orders.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Online shops & payments

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "deadlatch": {
      "command": "uvx",
      "args": [
        "deadlatch",
        "--policy",
        "your-value",
        "--portfolio",
        "your-value"
      ]
    }
  }
}

Run this in your terminal

claude mcp add deadlatch -- uvx deadlatch --policy your-value --portfolio your-value

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "deadlatch": {
      "command": "uvx",
      "args": [
        "deadlatch",
        "--policy",
        "your-value",
        "--portfolio",
        "your-value"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "deadlatch": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "deadlatch",
        "--policy",
        "your-value",
        "--portfolio",
        "your-value"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Diabloluo, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

More stars than 0% of the other 1749 servers in this category
Published to the registry more recently than 42% of the other 1749 servers in this category
Basic checks equal to or better than 100% of the other 1749 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Deadlatch safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry last month.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spree Commerce: open-source B2B and marketplace ecommerce

by spree

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

Runs in the cloud★ 15,812BSD-3-ClauseUpdated 7 days ago

Install

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago

Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 27 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Deadlatch

The pre-trade latch for your trading agent. Advisory-only.

Three things you need to know before anything else:

You need an independent, cross-broker gate that you control. If an agent can place orders on your account, the last check between the agent and the broker should not be the agent itself — and it should not be locked to one broker's UI or rules.
Deadlatch does not predict, does not recommend, and does not place orders. It answers one question only: *is this order allowed right now?* It is not a signal generator and it is not a broker.
Every answer comes with reasons, evidence, and a local audit record on Linux/macOS. PASS / WARN / BLOCK is never a bare verdict — you can see which rule hit, why, and what was evaluated. Durable audit writes (init / append / repair / prune / shadow report) are supported on Linux and macOS only. On Windows the package still imports, and the rule engine / Guard / CLI / MCP still compute decisions; those write paths fail closed with audit_platform_unsupported. Offline verify / read of a stopped snapshot remain available. Windows MCP is a limited integration path, not a full trusted audit chain.

Honest boundary (please read): Deadlatch is advisory. It cannot force an agent that never calls it to call it, and it cannot stop an agent that ignores a BLOCK from submitting the order somewhere else. Whether the agent calls the guard and honors the result is the integrator's decision. Do not rely on this tool as a guarantee against loss — it is a gate, not an insurance policy.

License: MIT — see LICENSE.
中文文档: README.zh-CN.md
Security: SECURITY.md · Contributing: CONTRIBUTING.md · Disclaimer: DISCLAIMER.md

Start here

The current install path is the verified PyPI deadlatch==0.1.2, published on 2026-09-22. The stable GitHub v0.1.2 Release targets b072e8a4d4b053e1d5a428dbb9c47e06652fbf4c; its wheel/sdist assets match the PyPI originals.

pip install deadlatch==0.1.2

The published MCP Registry name is io.github.Diabloluo/deadlatch at version 0.1.2, verified active/latest on 2026-09-22. The local server.json matches that published version. The command below starts the verified PyPI package directly.

MCP-first start:

uvx --from deadlatch==0.1.2 deadlatch-mcp --policy policy.yaml --portfolio portfolio.json

--policy and --portfolio are required local files. --audit-path and --kill-switch-path are optional. Use fictional or your own simulated inputs only. Deadlatch is advisory-only: it never places orders and cannot stop an agent that never calls it. Option orders must use the broker's unique full contract code as symbol. A historical GitHub pre-release remains at v0.1.0.dev1; it is not the current install path.

Then:

Run a fictional-data Quick Start below (Python, CLI, or MCP) on Linux or macOS. Confirm PASS → BLOCK → local audit. Windows can import the package and run rule computation; it is not the audit-write Quick Start.
Request a 20-minute integration assessment only if you already have an order-intent or simulated execution path: open the assessment form.

That GitHub issue is public. Do not paste accounts, positions, orders, API keys, tokens, customer names, or private paths. Security defects must go through GitHub Security Advisories, not a public issue.

Quick Start (60 seconds each)

All three quick starts use fictional data and a temporary audit path. They are executed from the same source scripts by the test suite, so they cannot drift from the documentation. Full audit-write / MCP Quick Start requires Linux or macOS. Windows may import the library and evaluate rules; it will not initialize or append a durable audit collection.

1. Python API

pip install dist/deadlatch-*.whl        # or: pip install -e .

python docs/quickstart/python.py

Shows Guard.from_policy(...) → Order / Portfolio → guard.check(...): a valid order returns PASS / 0; an oversized order returns BLOCK / 3 with the hit rules; on BLOCK the example caller stops — no broker call is ever made.

2. CLI

bash docs/quickstart/cli.sh                  # requires `deadlatch` on PATH

Creates fresh inputs in a temp directory (dynamic timestamps — never goes stale), then runs deadlatch check for PASS (exit 0), BLOCK (exit 3), an input error (exit 4), and a --json check, plus shadow report --json over the audit.

3. MCP (stdio)

python docs/quickstart/mcp_client.py         # requires `deadlatch` installed

Starts deadlatch-mcp as a real subprocess over stdio, lists the five tools, and calls check_order once for PASS and once for BLOCK. policy / portfolio / audit paths are server startup configuration — an agent cannot swap them as tool arguments. BLOCK is a constraint the caller must honor; technically the guard cannot force a fully bypassing agent to call it.

What it is / is not

Deadlatch is	Deadlatch is not
A local, deterministic risk gate evaluated before you submit	A signal generator, recommender, or portfolio optimizer
A library, a CLI, and a stdio MCP server — no broker connectivity, no policy mutation	A broker adapter, an execution engine, or a market feed
An auditable check: every evaluation is written to a local JSONL log	A cloud service, a database, or a telemetry sink
USD-only, single-leg orders, one snapshot per check (v0.1)	Multi-leg, multi-currency, Greeks/IV-aware (see limitations)

Who should use it

Teams that already have an order-intent or simulated execution path and want an independent, deterministic pre-trade gate with a local audit trail.
Developers who want a small, dependency-light, fail-closed building block they can integrate into their own execution pipeline.
Anyone who wants to evaluate orders against a *policy they control*, expressed as plain YAML.

Who should not use it: anyone expecting a profit guarantee, a backtest engine, a portfolio manager, or a tool that enforces itself. If the agent never calls the guard, or ignores a BLOCK, nothing in this repository can stop it.

Core security boundary

Local: everything runs on your machine; no account credentials are ever stored, read, or transmitted.
No network core path: the library, CLI, and MCP server never open a socket, never register an HTTP/SSE route, and never call out for quotes or anything else (the MCP SDK's HTTP stack is a transitive dependency that business code never imports).
Never places orders: the core package (library, CLI, MCP server) has no broker connectivity and never submits orders. Experimental read-only mapping examples exist only in the development workspace; they are not included in the public candidate or the wheel, and they are not live-verified integrations.
Fail-closed: missing or malformed data → BLOCK (exit 3); input/config errors → exit 4; internal errors → exit 5. An uncertain state is never reported as PASS.
Direction is snapshot-derived: order-side text is never accepted as proof of a close. Stock and option closing intent is recognized only when a fresh portfolio snapshot contains a matching, opposite-side position with sufficient quantity. For options, symbol must be the broker's unique full contract code; never reuse an underlying ticker across different expiries, strikes, or rights.
USD-only (v0.1): any currency mismatch (order, portfolio, positions) is an input error (exit 4); the MCP account-status tool fail-closes on mismatch.

Write surface: the tool never modifies policy, portfolio, or kill-switch state, never connects to a broker, and never places an order. Two kinds of intentional local file writes exist:

Audit subsystem: Guard.check() / check_order append one sanitized v2 record to a UTC day shard next to the logical audit path (30-day retention). Append is a bounded tail write under a shared lock; it does not rewrite history. A new collection needs one explicit deadlatch audit init (or initialize_audit_state) before append; Guard/MCP never auto-migrate. deadlatch shadow report and deadlatch audit prune delete whole shard files that fall outside the 30-calendar-day window. deadlatch audit repair --quarantine still uses lock/tmp files and os.replace when it isolates a truncated tail. Ordinary append is not crash-atomic across files. POSIX locks are cross-process. v0.1.2 durable audit writes are Linux/macOS only; Windows writers receive audit_platform_unsupported and do not skip directory fsync to report success.
Explicit migration output: deadlatch migrate --output writes the migrated document only when you explicitly pass --output.

The public contract for these rules, Decimal thresholds, exit codes, and option-symbol requirements is docs/rules-spec.md.

The 12 rules (v0.1)

#	Rule	What it guards
R1	`kill_switch`	Global switch: `off` / `full` (block everything) / `reduce_only` (allow only inferred closing orders)
R2	`input_validity`	Order passes schema, version gate, currency consistency, finite amounts (violations → `exit 4`)
R3	`max_order_quantity`	Single-order quantity limit
R4	`max_order_value`	Single-order notional limit (options: price × multiplier × quantity)
R5	`max_symbol_exposure`	Exposure per underlying (options by strike × multiplier × quantity)
R6	`max_total_exposure`	Portfolio gross exposure ratio
R7	`cash_margin_check`	Post-trade cash floor and short-option margin
R8	`max_daily_loss`	Daily loss ratio (PnL / day-start equity)
R9	`max_drawdown`	Drawdown ratio from peak
R10	`order_time_validity`	Order age / future timestamps (unparseable → fail-closed BLOCK)
R11	`data_freshness`	Portfolio snapshot freshness (future snapshot → fail-closed)
R12	`missing_data_fail_closed`	Missing/null/ill-formed portfolio data → `exit 3` (data unusable = risk)

Optional rules (R3–R7) are toggled by their config keys in policy.yaml; a missing optional key must be declared in acknowledged_disabled or the policy is rejected (exit 4). Mandatory rules (R1, R2, R8–R12) can never be disabled.

Exit codes

Code	Meaning
`0`	PASS — the order is allowed as given
`2`	WARN — proceed only if your execution policy explicitly allows warnings
`3`	BLOCK — the order must not be submitted (risk rule or fail-closed data)
`4`	Input / configuration error — the caller misused the API, not a risk event
`5`	Internal / rule exception — treated as BLOCK (fail-closed)

In shadow mode the internal verdict is recorded (shadow_verdict) while the external projection is PASS / 0; kill-switch hits and exit 4/5 are never projected away.

Data contracts & migration

Schemas are versioned JSON Schema 2020-12 files shipped inside the package: order, portfolio, policy, result, audit-record, shadow-report, audit-maintenance-result, audit-prune-result, audit-write-state, audit-state-result. Explicit offline migration is available for legacy documents:

deadlatch migrate --kind order    --input order_v1.json    [--out

Only the beginning is shown; read the rest in the repo

Deadlatch

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

MCP Cn Commerce

README from the maker

Deadlatch

Start here

Quick Start (60 seconds each)

1. Python API

2. CLI

3. MCP (stdio)

What it is / is not

Who should use it

Core security boundary

The 12 rules (v0.1)

Exit codes

Data contracts & migration