Ext Ops Panel
Open dashboard
Comparison

writ vs AXIOM

writ is an MCP server published by AvenueDAdmin. Marketplaces we read that list it: 1 (Official MCP Registry). AXIOM is an MCP server published by dragoscv. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplacewritAXIOM
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 488
Downloads/week (PyPI): 39
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 3.0.0
Downloads/month (npm): 2 107
Downloads/week (npm): 436
Forks (GitHub): 0
Stars (GitHub): 0
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

writ vs AXIOM
FactwritAXIOM
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-19
Where it runs (differs)On your machine (writ-mcp)On your machine (@codai/axiom-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 21, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/avenuedadmin/pywritgithub.com/dragoscv/axiom
Changes in the last 7 days (differs)08
First seen2026-10-112026-10-11

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

writ

In its own words, on Official MCP Registry:

Commit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log.

AXIOM

In its own words, on Official MCP Registry:

Transactional write gate for coding agents: plan, canonical manifest, checks, two-phase apply.

How to run each

writ As a local MCP server: PyPI package

Claude Code
claude mcp add --env "WRIT_API_KEY=<YOUR_WRIT_API_KEY>" --env "WRIT_SPONSOR_TOKEN=<YOUR_WRIT_SPONSOR_TOKEN>" --transport stdio writ -- uvx writ-mcp

Requires: WRIT_API_KEY (secret), WRIT_SPONSOR_TOKEN (secret)

AXIOM As a local MCP server: npm package

Claude Code
claude mcp add --env "AXIOM_SIGNING_KEY=<YOUR_AXIOM_SIGNING_KEY>" --transport stdio axiom -- npx -y @codai/axiom-mcp mcp --root "<YOUR_ROOT>"

Requires: AXIOM_SIGNING_KEY (secret), --root

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

Tools each declares

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

Settings each asks for

Only writ asks for

  • WRIT_API_KEY (secret)
  • WRIT_BASE_URL
  • WRIT_SPONSOR_TOKEN (secret)

Only AXIOM asks for

  • AXIOM_SIGNING_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: writ · What it can do: AXIOM · 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