Inspect an MCP server for common security risks before you install it. Offline, zero telemetry.
MCPpedia last refreshed this data
io.github.mcpcustoms/mcp-customs is an MCP server that inspect an MCP server for common security risks before you install it. Offline, zero telemetry. Its tool list has not been published yet over stdio and http, requires no API key, and scores 56/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-mcpcustoms-mcp-customs": {
"args": [
"-y",
"mcp-customs"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Inspect an MCP server for common security risks before you install it. Runs fully offline. No telemetry, no cloud upload, no account.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-customs' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-customs against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
MCP Server for GCP environment for interacting with various Observability APIs.
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
MCP Security Weekly
Get CVE alerts and security updates for io.github.mcpcustoms/mcp-customs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Inspect an MCP server for common security risks before you install it. Runs fully offline. No telemetry, no cloud upload, no account.
npx mcp-customs scan ./some-mcp-server
──────────────────────────────────────────────────────
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 ...
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.
| 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."
# .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
npx mcp-customs scan . --badge --name your-server-name
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.