MCP security: start with your configuration

A configuration review can reveal choices worth investigating. It cannot establish that a running server, its dependencies, or the systems it accesses are secure.

Use a risk framework to organize the review

The OWASP MCP Top 10 describes risks including secret exposure, excessive privileges, tool poisoning, and supply-chain attacks. ShieldMCP groups static configuration heuristics around its 2025 categories. This mapping is not OWASP certification or comprehensive coverage of each risk.

What ShieldMCP checks

The scanner examines submitted configuration text for patterns such as plaintext credentials, broad filesystem paths, unpinned packages, and suspicious command arguments. Findings are prompts for a review, and can include false positives. A score is a heuristic summary, not a measured probability of compromise.

What remains outside the scan

ShieldMCP does not connect to MCP servers, execute tools, inspect installed package source, test tenant isolation, or verify runtime authorization and logging. Missing configuration settings do not prove those controls are absent. A result with no flags does not prove a setup is safe.

Review a sanitized copy

Configuration text is sent to our server for analysis. Replace real credentials and sensitive details before submitting. Read the privacy notice for storage and report-link handling.