MCP Tool Auditor
Related Servers
Alternatives to MCP Tool Auditor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceScores MCP tool definitions and tool lists from 0-100, flagging vague descriptions, missing parameter docs, non-verb-first naming, oversized enums, and nested schemas with severity, rationale, and concrete fixes. It also validates marketplace listings against platform character caps such as MCPize's 500-character short-description limit before deploy.MIT
- AlicenseAqualityCmaintenanceStatic security linter for MCP servers. Scans tool definitions for vulnerabilities (path traversal, SQL injection, SSRF), scores description quality, and auto-rewrites descriptions for safer agent tool selection.2188 PyPI10MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to grade MCP tool definitions for agent-readiness, returning a score, A–F grade, concrete fixes, and estimated token cost.MIT
- AlicenseNot gradedqualityAmaintenancePerforms explainable, deterministic static analysis of MCP tool metadata to detect misleading instructions, concealed capabilities, and schema drift without executing tools.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables an agent or MCP client to scan MCP server configs and AI-agent tool manifests on demand, exposing tools that list detection rules and report hidden prompt injections, data-exfiltration attempts, embedded secrets, deceptive Unicode, unpinned packages and shell-launching tools. Each finding comes with a severity and location so risky tool descriptions can be caught before an attacker exploits them.186 PyPIApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables auditing MCP servers' tools by their estimated context token cost, ranking verbose names, descriptions, and schemas before they consume the agent window. Can run as an MCP tool so agents can budget their own context.1MIT
TDQS
Scored across 4 tools
Audit_tool and audit_tool_list overlap in purpose (auditing descriptions) but are clearly separated by scope (single vs. list). Rewrite and best practices are distinct. The descriptions make the boundaries clear, so confusion is unlikely.
All tool names follow a consistent verb_noun pattern in snake_case (audit_tool, rewrite_tool_description, audit_tool_list, get_best_practices). No mixed casing or stylistic deviations.
Four tools is well-scoped for the server's purpose. Each tool addresses a distinct step in the auditing workflow: reference, single audit, batch audit, and rewrite.
The core workflow is covered: get best practices, audit individual or list, and rewrite weak descriptions. A minor gap is lack of a validation/apply tool after rewriting, but the existing set supports the main use case effectively.