MCP Config Guard - agent config lint
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Reads .mcp.json / .vscode/mcp.json / claude_desktop_config.json while you edit it and marks the lines that hand an AI agent more than you meant - unpinned servers, literal credentials, plaintext transport, whole-home filesystem roots. 23 rules, offline, no server is ever started.
Install
mcp-config-guard file
Node 18+. The same 23 rules as the VS Code extension, from a terminal or CI.
Free
- Check the MCP config file you have open against all 23 rules - the line number, one sentence on what goes wrong, and the line that replaces it - offline, no key, no limit.
--ruleslists every rule
With a licence ($29 once)
- Scale and hand-off: one sweep over every MCP config in the workspace and in the client config folders, a dated CSV/JSON/HTML report, and machine-readable output a CI step can fail on.
mcp-config-guard --dir ./templates --report html --out report.html
Upwork lists cybersecurity developers at a $60 median hourly rate, $40-$90 typical (Sept 2026).
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "mcp-config-guard": { "command": "mcp-config-guard", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: MCP Config Guard - agent config lint
run: pip install rulestamp-mcp-config-guard && mcp-config-guard --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-mcp-config-guard
mcp-config-guard --help
Metadata
Release files for rulestamp-mcp-config-guard 1.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_mcp_config_guard-1.0.8.tar.gz | 19.6 kB | Without provenance | Details for rulestamp_mcp_config_guard-1.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_mcp_config_guard-1.0.8-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_mcp_config_guard-1.0.8-py3-none-any.whl |
Total release size: 41.4 kB
Release files / rulestamp_mcp_config_guard-1.0.8.tar.gz
| Download URL | rulestamp_mcp_config_guard-1.0.8.tar.gz |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f214cd118ee3ebe6bbcfd9b2af130524198429211e2bfee312747913b5c0519
|
|
BLAKE2b-256 checksum How to use checksums |
bb58bb24c3c47c1d645b04f679e0a36da0f72e0ff03a1cb7c9ddb28ac37517f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_mcp_config_guard-1.0.8-py3-none-any.whl
| Download URL | rulestamp_mcp_config_guard-1.0.8-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a39f5cf7a99e30c51d1043c438be1f4997dbebd59d0ab8955eadfbf79360402
|
|
BLAKE2b-256 checksum How to use checksums |
c314bf15bb8c8ade4afb64bc30cca58562eb757153c1a2010e30531d5ad43bf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-mcp-config-guard 1.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.