MCP Customs

Inspect an MCP server for common security risks before you install it. Offline, zero telemetry.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "mcp-customs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-customs"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

mcp-customs

Inspect an MCP server for common security risks before you install it. Runs fully offline. No telemetry, no cloud upload, no account.

Terminal

npx mcp-customs scan ./some-mcp-server

Code

──────────────────────────────────────────────────────
MCP-CUSTOMS INSPECTION REPORT
──────────────────────────────────────────────────────
target        ./some-mcp-server
files scanned 14
score         62 / 100
stamp         [ REVIEW ]
──────────────────────────────────────────────────────
[HIGH] MCP002 — Unsanitized file path (possible path traversal)
  server.js:41  return fs.readFileSync(userPath, 'utf8');
  fix: Resolve the path against an allowed base directory ...

Why

Developers install MCP servers the way they used to install npm packages — quickly, trusting the name, and moving on. An MCP server can read your files, call your APIs, and execute commands on your behalf. Almost nobody checks what it can actually do before connecting it to their agent.

mcp-customs is the "audit before install" step, run locally, in seconds.

What it checks (v0.1)

Rule	Severity	What it looks for
MCP001	critical	Shell command execution with unsanitized interpolation
MCP002	high	File reads/writes without a path-traversal guard
MCP003	critical	`eval()` / dynamic code execution
MCP004	high	Hardcoded API keys / credentials
MCP005	critical	Tool descriptions containing hidden-instruction language (prompt injection via the tool's own metadata)
MCP006	medium	Outbound network calls combined with environment-variable reads (possible exfiltration)
MCP007	low	No permissions/scopes declared in the manifest

These are heuristic, regex-based checks — fast and fully auditable in one sitting, not a dataflow analysis. They will produce false positives and will miss things a deeper analysis would catch. Treat a CLEARED stamp as "nothing obvious," not "verified safe."

CI usage

yaml

# .github/workflows/mcp-customs.yml
- run: npx mcp-customs scan . --sarif results.sarif --fail-on high
- uses: github/codeql-action/upload-sarif@v3
  with:
    sarif_file: results.sarif

Get a badge for your README

Terminal

npx mcp-customs scan . --badge --name your-server-name

Roadmap

Publish scan results to a public registry (mcp-customs.dev) with searchable trust scores
Dynamic/sandboxed analysis (catch what static checks miss)
Python-specific AST checks (current Python rules are regex-only)
Community flagging / verification on registry entries

License

Apache-2.0. No open-core trap — this CLI stays free either way. If a hosted registry/dashboard ships later, that's a separate paid product; this tool's local scanning will never require it.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about MCP Customs

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "mcp-customs": { "command": "npx", "args": ["-y", "MCP Customs"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/mcp-customs?style=directory)](https://allmcps.com/mcp/mcp-customs)

HTML Embed

<a href="https://allmcps.com/mcp/mcp-customs"><img src="https://allmcps.com/api/badge/mcp-customs?style=directory" alt="MCP Customs on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

37Quality signal: Fair · 37/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to MCP Customs →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

mcp-customs

Inspect an MCP server for common security risks before you install it. Runs fully offline. No telemetry, no cloud upload, no account.

Terminal

npx mcp-customs scan ./some-mcp-server

Code

──────────────────────────────────────────────────────
MCP-CUSTOMS INSPECTION REPORT
──────────────────────────────────────────────────────
target        ./some-mcp-server
files scanned 14
score         62 / 100
stamp         [ REVIEW ]
──────────────────────────────────────────────────────
[HIGH] MCP002 — Unsanitized file path (possible path traversal)
  server.js:41  return fs.readFileSync(userPath, 'utf8');
  fix: Resolve the path against an allowed base directory ...

Why

mcp-customs is the "audit before install" step, run locally, in seconds.

What it checks (v0.1)

Rule	Severity	What it looks for
MCP001	critical	Shell command execution with unsanitized interpolation
MCP002	high	File reads/writes without a path-traversal guard
MCP003	critical	`eval()` / dynamic code execution
MCP004	high	Hardcoded API keys / credentials
MCP005	critical	Tool descriptions containing hidden-instruction language (prompt injection via the tool's own metadata)
MCP006	medium	Outbound network calls combined with environment-variable reads (possible exfiltration)
MCP007	low	No permissions/scopes declared in the manifest

CI usage

yaml

# .github/workflows/mcp-customs.yml
- run: npx mcp-customs scan . --sarif results.sarif --fail-on high
- uses: github/codeql-action/upload-sarif@v3
  with:
    sarif_file: results.sarif

Get a badge for your README

Terminal

npx mcp-customs scan . --badge --name your-server-name

Roadmap

Publish scan results to a public registry (mcp-customs.dev) with searchable trust scores
Dynamic/sandboxed analysis (catch what static checks miss)
Python-specific AST checks (current Python rules are regex-only)
Community flagging / verification on registry entries

License

Apache-2.0. No open-core trap — this CLI stays free either way. If a hosted registry/dashboard ships later, that's a separate paid product; this tool's local scanning will never require it.