All MCP Servers
Dev Tools & GitMCP RegistrypypiB · 79

ZeroDOM MCP server

io.github.DevHusnainAi · Updated

The deterministic attack-surface perception layer for AI security agents

At a glance

ZeroDOM is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `uvx zerodom`, and declares no required credentials. It scores B (79/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 3GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install ZeroDOM in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install ZeroDOM in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add zerodom -- uvx zerodom
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What tools does ZeroDOM expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 5 of 5 source files.

Nothing in this package's own source reaches for the filesystem, the network, or other programs.

How it was published

  • Published by a verified CI identity (github trusted publishing) rather than a personal token.
  • Has a provenance attestation tying this artifact to the commit it was built from.
  • 2 npm maintainers · last published by GitHub Actions.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit today — Actively maintained.
  • Repository created 2 months ago — Very new project with little track record yet.
  • 3 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 79

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%18%

    3 stars.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%100%

    Package and registry entry point at the same repository.

  • Packaging15%100%

    Publishes a pinned version (0.1.4).

Documentation

Full README

ZeroDOM

Point it at an app as two users. It finds the broken access control.

ZeroDOM drives your real, logged-in browser as two identities, replays the same requests as each, and flags where one user reaches what another can't — IDOR / broken access control, caught deterministically. Open-core, runs local, no account, no API key, nothing leaves your machine.

<sub>Under the hunt is a deterministic, token-lean perception engine for AI agents — the same core powers <code>scan</code>, <code>crawl</code> and any browser-driving task. IDOR is just where it bites hardest.</sub>

[Site](https://zerodom.vexralabs.com) · [Docs](https://zerodom.vexralabs.com/docs) · [Playground](https://zerodom.vexralabs.com/playground) · [Discord](https://discord.gg/tVRznUb5Ez) · [Quickstart ↓](#quickstart)

<sub>A normal user is <b>denied</b> the admin console (401) — then walks in by flipping one client-controlled cookie. ZeroDOM proves it: same request, two identities, <b>401 vs 200</b>. Full recording (mp4).</sub>


Contents

  • Why ZeroDOM
  • Quickstart
  • How it hunts — `compare` & `sweep`
  • Use it from an AI agent (MCP)
  • Why the agent sees so few tokens
  • More of the CLI
  • How it compares
  • Install
  • Security & scope
  • Limitations
  • Editions
  • Contributing & development
  • License

Why ZeroDOM

Two audiences, one engine:

  • AppSec — [`compare` / `sweep`](#how-it-hunts--compare--sweep): deterministic two-identity

authorization testing that runs headless in CI or your recon pipeline — no GUI, no account. scan --js adds DOM-XSS sinks, the callable API surface and header posture; repeat / probe / race turn recon into verification (Repeater, mass-assignment diff, and a TOCTOU burst).

Excerpt — the full document is on GitHub.

Maintain ZeroDOM? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![ZeroDOM on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-devhusnainai-zerodom)](https://mcp-skills-hub.vercel.app/mcps/io-github-devhusnainai-zerodom)

Catalog data refreshed . Something wrong? Report it.