mcp-latchpoint
mcp-latchpoint
mcp-latchpoint audits MCP client configuration files without running the configured servers. It works offline, reads only local files you select, and produces text, JSON, or SARIF results.
This is an early defensive tool. Review findings in context before changing a working configuration.
What it checks
The v0.1 rules cover:
plain HTTP for non-loopback remote endpoints
shell wrappers and inline shell control syntax
identifiable
npxanduvxpackages without exact versionsliteral credentials in environment values, headers, arguments, or URLs
filesystem roots and home roots passed as recognizable access scopes
wildcard hosts and recognizable wildcard scopes
conflicting, missing, invalid, or unsupported transport settings
Every finding has a stable rule ID, severity, location, remediation, redacted evidence, and a confidence note when interpretation depends on the launched server.
Related MCP server: mcp-audit
Install
Python 3.11 or newer is required.
python -m pip install mcp-latchpointTo install from a local checkout:
python -m venv .venv
# Linux or macOS
. .venv/bin/activate
# Windows PowerShell
.venv\Scripts\Activate.ps1
python -m pip install .For development:
python -m pip install -e ".[dev]"
pytest
ruff check .
mypyThe MCP server uses the official Python SDK v2 and the dependency is constrained to mcp>=2.3,<3.
CLI
Scan one or more explicit files:
mcp-latchpoint scan ~/.config/Code/User/mcp.json
mcp-latchpoint scan examples/risky.json --format json
mcp-latchpoint scan examples/risky.json --format sarif --fail-on high > results.sarifRestrict every explicit path to an approved directory:
mcp-latchpoint scan ./configs --allowed-root ./configsDirectories are searched only for recognized MCP config filenames, up to 256 files. A file is limited to 1 MiB by default. Change these bounds with --max-files and --max-bytes.
Exit codes are 0 for a completed scan below the chosen threshold, 1 when a finding meets --fail-on, and 2 for input, containment, or parse errors. The default --fail-on none reports findings without failing a build.
List and explain rules:
mcp-latchpoint rules
mcp-latchpoint explain MCP004Recognized layouts
Explicit files may use these structures:
Client layout | Container | Accepted file syntax |
Claude Desktop, Cursor, portable | top-level | JSON |
Claude Code user/local settings | top-level | JSON |
VS Code | top-level | JSONC for |
Codex |
| TOML |
Files ending in .jsonc are also parsed as JSONC. Other .json files remain strict JSON so malformed input is not silently accepted.
--discover checks only the following paths when they exist. It does not search the rest of the home directory.
All systems:
~/.claude.json,~/.cursor/mcp.json,~/.codex/config.toml,$COPILOT_HOME/mcp-config.jsonwith~/.copilot/mcp-config.jsonas the fallbackCurrent project:
.mcp.json,.codex/config.toml,.cursor/mcp.json,.vscode/mcp.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json,%APPDATA%\Code\User\mcp.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json,~/Library/Application Support/Code/User/mcp.jsonLinux:
$XDG_CONFIG_HOME/Code/User/mcp.json, falling back to~/.config/Code/User/mcp.json
Read-only MCP server
The stdio server exposes two tools: list_rules and scan. It requires an allowed root at startup. Relative scan paths are resolved below that root; absolute paths, .. traversal, and symlinks cannot escape it.
mcp-latchpoint-server --root /absolute/path/to/reviewed-configs
mcp-latchpoint serve --root /absolute/path/to/reviewed-configsExample client entry:
{
"mcpServers": {
"latchpoint": {
"command": "/absolute/path/to/mcp-latchpoint-server",
"args": ["--root", "/absolute/path/to/reviewed-configs"]
}
}
}The server returns findings and scan metadata, never raw configuration content. Stdio is the only server transport exposed by the entry point, and stdout is reserved for MCP protocol messages.
The serve command is also the entry point advertised in the MCP Registry. Set --root to a directory you explicitly trust before connecting a client.
Glama build
The Glama listing builds a container from the repository. In its Dockerfile configuration, use Python 3.13, these build steps and command arguments:
["uv sync --no-dev"]["mcp-proxy", "--", "/app/.venv/bin/mcp-latchpoint-server", "--root", "/app/examples"]The root is an existing directory with synthetic sample configurations. It lets Glama start and inspect the tools without giving the server access to a user's files. The command uses the executable inside the virtual environment created by uv sync. For this demo, the environment-variable schema can be {"type":"object","properties":{}} and placeholder parameters can be {}.
To scan your own configurations, run the server locally with --root pointing to a directory you explicitly trust. Glama's demo root is only for the sample files in examples/.
Safety and limitations
The scanner never executes commands, installs packages, resolves referenced environment variables, or connects to endpoints. It does not follow configuration includes or inspect an MCP server's code or runtime behavior. Argument-based rules are intentionally limited to recognizable patterns, so custom flags can be missed. A clean report is not proof that a server is safe.
Secret detection is designed to emit field names and <redacted> markers rather than values. If you find a leak or a path-containment problem, follow SECURITY.md and do not attach a real configuration to a public issue.
License
MIT. See LICENSE.
Available Tools
2 toolslist_rulesA
List stable audit rule IDs, severity, descriptions, and remediation.
Inputs: no named parameters. Returns: object
scanC
Scan a config file or directory inside the server's allowed root.
Inputs: path (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
list_rules enumerates audit rules while scan analyzes a config file or directory—two clearly distinct purposes targeting different objects (rule metadata vs. actual files). No overlap or confusion.
list_rules follows a clean verb_noun pattern, but scan is a bare verb without a noun target, a minor deviation from the convention. Still readable and predictable overall.
Two tools is borderline thin for an audit/lint server; listing rules and running a scan are essential, but the surface feels minimal for the apparent scanning domain.
The core discover-then-scan workflow exists, but there's no way to fetch a single rule's detail, filter by severity, or apply/view remediation beyond what list_rules returns. Notable gaps limit deeper audit workflows.
Maintenance
Related MCP Connectors
Static MCP server scan: injection, secrets, tool poisoning. Report + SARIF + CI.
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Scans remote MCP servers for protocol, security, and TLS issues; exposes scan tools via MCP.
Free, read-only security scanner for remote MCP servers, before you connect them.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceScans MCP servers for security hardening issues including capability declarations, transport, and tool descriptions.1-
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.182 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations and packages for security risks such as typosquats, credential exposure, and malicious code, with zero dependencies and no execution.1MIT

Bounce Watch MCPofficial
AlicenseAqualityCmaintenanceTracks buying and momentum signals for companies, such as funding rounds, senior hires, office openings, customer wins, and partnerships, with each event carrying its date.1014 npmMIT