$ loading_
Statically inspects MCP tool metadata for misleading instructions, hidden capabilities, and schema drift.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "MCP Tool Security Inspector" yet — see the docs or source repo.
Please perform an explainable static analysis of this MCP tool metadata. Check for misleading instructions, concealed capability descriptions, and schema drift risks, then list evidence and conclusions by issue type.
A static analysis report organized by risk type, showing issues found, supporting evidence, and rationale.
Without executing the tool, inspect whether this MCP tool metadata matches its claimed capabilities, whether any descriptions may mislead models or users, and identify fields that should be corrected.
A pre-release validation checklist highlighting inconsistencies, misleading items, and suggested fixes.
Analyze whether this MCP tool metadata shows schema drift, such as changed field meanings, mismatches between declarations and structure, or risks caused by metadata evolution. Please provide a deterministic conclusion.
A schema drift assessment with specific drift points and their potential impact.
Developers or security reviewers can statically inspect metadata before integrating third-party MCP tools to catch misleading instructions or concealed capability descriptions and reduce integration risk.
MCP tool maintainers can use it before release to verify that metadata aligns with stated capabilities and to detect possible schema drift issues.
Researchers can use its explainable, deterministic static analysis to compare safety risk patterns across different MCP tool metadata sets.
It performs explainable, deterministic static analysis of MCP tool metadata to detect misleading instructions, concealed capabilities, and schema drift. It does not execute the tool itself.
No. The description explicitly says it performs static analysis without executing tools.
Based on the provided description, it mainly checks three issue types: misleading instructions, concealed capabilities, and schema drift. For more details, see the source repository.
Analyze MCP tool security risks, detect malicious behavior, and provide risk scores.
Statically audit MCP tool surfaces for token cost, schema quality, and design issues.
Use safe MCP tools for calculation, search, drift checks, eval comparison, and grading.
Scan MCP tool descriptions for prompt injection and privilege escalation risks.
An MCP tool for threat modeling, security review, and compliance governance.
Scan MCP servers for runtime, static, config, dependency, and compliance risks.