mcp-security-auditor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_pathB | Run static Python AST, MCP schema, prompt-injection, and Firebase rules security scan on a local directory or file (secrets redacted by default). |
| list_security_rulesA | List all 13 CWE-mapped static security rules implemented by mcp-agent-security-auditor. |
| remediate_pathB | Automatically redact hardcoded secrets or restore clean static redirect index.html in a local directory or file before git push. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: scanning, listing rules, and remediation. An agent should have no trouble choosing between them.
All tools use consistent snake_case verb_noun naming: scan_path, list_security_rules, remediate_path. The pattern is predictable and readable.
Three tools is a focused, reasonable surface for a local security auditor, and each earns its place. It is slightly thin, with no dedicated reporting or configuration tool.
The set covers scanning, rule discovery, and basic remediation, which are the core workflows. Minor gaps exist around exporting reports, configuring rule sets, or verifying remediation results.