$ loading_
Scan MCP servers for hardening issues in capabilities, transport, and tool descriptions.
The available materials describe an open-source MCP hardening scanner with no required secrets and no declared remote endpoints, with no clear high-risk red flags. However, because it can execute code and lacks a README while adoption and maintenance signals are weak, it should be reviewed and used in an isolated environment.
The materials explicitly state that no keys or environment variables are required, and no API keys, tokens, or other sensitive credentials are requested, so credential exposure risk appears low.
The declared remote endpoint host is 'none', and the description only mentions scanning MCP server hardening aspects; there is no evidence in the materials of sending user data to third-party services or unknown endpoints.
The system checks indicate it has executes-code capability, meaning it can run code locally or initiate scanning logic; this is a normal higher-privilege capability for an MCP tool and warrants attention to actual system access and runtime boundaries, but by itself does not justify a high-risk rating.
The description says it scans MCP servers for capability declarations, transport, and tool descriptions, implying at least read access to exposed server configuration or metadata; the materials do not specify what local files or data it may read or write, so its actual access scope should be verified.
Positive signals include being open source under the MIT License, which makes source review possible; however, it comes from a third-party registry, has 0 stars, unknown maintenance status, and no README, so supply-chain maturity and transparency are limited and source/dependency review is advisable.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcpharden" yet — see the docs or source repo.
Scan this MCP server for security hardening issues. Focus on whether capability declarations follow least privilege, whether the transport is secure, and whether tool descriptions are misleading or overexpose information. List findings by severity with remediation advice.
A severity-ranked security review with findings, risk explanations, and remediation recommendations.
Analyze all tool descriptions in this MCP server and identify wording that could cause permission misunderstanding, vague usage, sensitive information leakage, or overprivileged invocation risks. Provide safer and clearer rewrite suggestions.
A risk list for tool descriptions, plus improved rewrite suggestions for each one.
Before releasing this MCP server, run a security self-check covering capability declarations, communication transport, tool descriptions, and overall hardening status. Output a checklist suitable for pre-release remediation.
A pre-release security remediation checklist to help the team harden and fix issues quickly.
Scan MCP servers for runtime, static, config, dependency, and compliance risks.
Scan MCP tool descriptions for prompt injection and privilege escalation risks.
Scan configured MCP servers locally and generate inventory with risk scores.
Scan remote MCP servers for protocol, security, and TLS issues.
Run comprehensive network scans and port discovery through an MCP server.
Scan codebases for secrets, SAST issues, vulnerable dependencies, and IaC risks.