mcp-audit

Name: mcp-audit
Author: saagpatel

by saagpatelversion 3.0.0i★ –iRuns on your computer

Registry nameio.github.saagpatel/mcp-audit

Install

Overview

Description from the maker (original English)

Scan, enumerate, and risk-score every MCP server configured on your machine.

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: Other

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": {
    "audit": {
      "command": "uvx",
      "args": [
        "mcp-audits",
        "serve"
      ]
    }
  }
}

Run this in your terminal

claude mcp add audit -- uvx mcp-audits serve

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "audit": {
      "command": "uvx",
      "args": [
        "mcp-audits",
        "serve"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "audit": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-audits",
        "serve"
      ]
    }
  }
}

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account saagpatel, 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 Otheri

More stars than 0% of the other 32476 servers in this category
Published to the registry more recently than 86% of the other 32476 servers in this category
Basic checks equal to or better than 100% of the other 32476 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 mcp-audit 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 (3.0.0) reached the registry 5 days ago.

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: Spec Driven Development, Remote Desktop Commander, zanadir

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

zanadir

by MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

Runs on your computerUpdated today

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.

mcp-audit

See what your AI tools' MCP servers can reach.

MCPAudit reviews MCP server configuration and, when asked, lists the tools a server exposes. It highlights declared capabilities, instruction-shaped text heuristics, and changes from a saved pin so you can decide what to investigate. Findings are review signals: a high score means broader capability exposure, not that a server is malicious or unsafe.

[!IMPORTANT]

The package is mcp-audits; the command is mcp-audit.

The default check is static. check --connect and --connect-all can start

configured local programs or contact configured endpoints. Legacy scan never

connects: it refuses connecting forms with exit 2 before discovery. Package

verification, downloads, and LLM analysis are separate opt-in operations.

MCPAudit does not edit configs, and reports environment variable key names,

never their values. Review generated reports before sharing them.

Try it

mcp-audit                              # static review of supported configs

mcp-audit check --config ./mcp.json # review this file only; no connections mcp-audit demo # see a bundled synthetic example mcp-audit explain MCP007 # explain a finding offline; no config reads

Install with uv:

uv tool install mcp-audits

Or run without installing:

uvx --from mcp-audits mcp-audit demo

What to do with a finding

Start with the suggested action and inspect the named capability or evidence. For example, if a filesystem server can write broadly, restrict its configured directory and review the report again. Pattern-based instruction checks can miss reworded or obfuscated text and can also need human review. A clean report is not a safety certificate.

Review the server's configured access, narrow it if needed, then run the check again.

Use Start here for a guided walkthrough and Reading results to interpret scores, findings, and coverage. How it works explains the check boundary.

Each rule's meaning, possible consequences, manual fix and confidence limits are in the finding reference; mcp-audit explain MCP013 prints the same entry offline. Explicit --config sources are labeled "explicit file; parsed as Claude-style config"; the parser identity does not establish which client uses that file.

Static tool metadata checks also flag malformed MCP header annotations, credential parameters mapped to headers, external schema references and unexpected icon sources. These checks inspect served metadata without fetching schemas or icons.

Use in CI

MCPAudit can write SARIF and evaluate local policy files. Begin with config-only CI, then enable connected checks only where the workflow should start those servers. See the CI guide and policy examples.

For a pinned release example, the composite Action can upload SARIF to GitHub code scanning:

- uses: saagpatel/MCPAudit@v3.0.0

The release checklist calls out Action references so maintainers can update examples when a new public release is available. Review the action's permissions and inputs before enabling it in a repository.

Choose a review path

Goal	Starting point	What it does
Learn the output	`mcp-audit demo`	Uses bundled synthetic input
Review one file	`mcp-audit check --config FILE`	Static check of the selected config
Make a share card	`mcp-audit checkup --config FILE --card checkup.html`	Writes a local counts-only HTML Preview
See discovered sources	`mcp-audit inspect`	Lists identities and source status
Inspect one server	`mcp-audit check --connect --server ID`	Connects to one unambiguous identity
Inspect a fleet	`mcp-audit check --connect-all`	Connects to workstation servers; add `--connect-project-configs` for projects
Automate a policy	`mcp-audit check --policy FILE`	Evaluates a local policy
Review a saved pin	`mcp-audit pin --status`	Shows baseline status; `pin` is the visible alias for `baseline pin`

The server ID is CLIENT:SCOPE:NAME; use the exact identity from inspect to avoid ambiguous selections. Connected checks can start configured local commands or contact their endpoints.

checkup writes a local, counts-only share card with no names by default; see the checkup guide.

Keep the evidence in context

Configuration-based findings describe declared access. A connected listing adds the tool metadata the server provides, but does not prove what the server will do later. Connected HTTP scans also send one credential-free server/discover request and, on 401, review bounded public authorization metadata. The probe never uses configuration header values and does not run with --skip-connect or for project sources without connection opt-in. These observations do not prove a completed OAuth flow. The optional canary is bounded and exercises only eligible tools under its documented limits. See How it works for the boundary between those observations.

Reports can contain configuration shape, tool names, and evidence text. Secret redaction is best-effort (known issues); review a report before sharing it. Configs are parsed in full, but environment variable values are discarded during parsing and never reported; reports keep key names for context. The output contract lists stable fields and the limits of these outputs.

Status

Stack

MCPAudit uses Python 3.11+, uv, pytest, Ruff, and mypy. JSON, SARIF, and HTML reports are versioned public surfaces. Run make check before proposing changes.

Known risks

Static findings describe configured access and served metadata; they do not prove how a server behaves later. Secret redaction is best-effort. Upgrading from 2.x? Read the 3.0 migration guide; the 3.0 boundary proposal records the decisions behind it.

Next steps

Use explicit synthetic fixtures for local changes, preserve read-only defaults, and keep coverage claims tied to completed checks. Re-enable Python 3.15 after an rpds-py/PyO3 lock refresh.

mcp-audit

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 Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

zanadir

README from the maker

mcp-audit

Try it

What to do with a finding

Use in CI

Choose a review path

Keep the evidence in context

Status

Stack

Known risks

Next steps

More documentation