Skill Quality MCP
Related Servers
Alternatives to Skill Quality MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAudits AI agent skills for safety using static, semantic, adversarial, and supply-chain analysis, providing scores and risk flags. Can be run via CLI, CI, or as an MCP tool from Claude Code, Cursor, and Codex.5170 PyPI2Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to inspect a project's design tokens and component catalog, audit React/Tailwind files against seven static UI quality rules, score overall UI health, and apply auto-fixes that are re-audited and reverted on regression. It works both locally over filesystem access and remotely on raw TSX/JSX or CSS snippets passed directly as strings.-
- AlicenseBqualityCmaintenanceEnables AI coding agents to perform evidence-based, read-only audits of supported software projects by exposing bounded project inventory and static-analysis findings for discovery, code review, integration tracing, security, and tests. Reports are returned as Markdown or JSON directly in the tool response, with no code executed or files written.817 npmMIT
- AlicenseAqualityBmaintenanceEvidence-backed, read-only codebase diagnostics for coding agents: secrets, dependency, RLS, and source-impact audits with a verify loop and PR review verdicts. Never writes files or uses the network by default.7101 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables authorized security auditing of AI-agent supply chains and agent-facing surfaces: deterministic local skill-bundle audits against eight attack patterns, secrets scanning, and scope-gated read-only recon of agent endpoints and MCP surfaces.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scan code for security and quality issues and receive machine-readable reports with suggested fixes and verification criteria.80 npm2MIT
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: skill listing/inspection, dependency analysis, local scanning, and a cohesive sonar_* cluster. Some overlap exists between code_quality_scan and sonar_issues (both surface bugs) and between sonar_issues and sonar_project_metrics, and full_quality_report aggregates the others, but descriptions clarify local vs. Sonar and aggregate vs. individual.
All snake_case throughout, with a predictable pattern: list_/inspect_/analyze_ verbs, sonar_-prefixed cluster, and full_quality_report. Minor deviation where code_quality_scan and sonar_project_metrics use noun-adjective ordering rather than verb_noun, but the grouping remains readable.
Nine tools is well within the ideal 3-15 range and each earns its place across skill, dependency, local scan, and Sonar workflows. The aggregate report tool is arguably redundant with the individual tools, but it serves a distinct one-shot use case.
The surface covers the full quality-check lifecycle: discover skills, inspect structure, analyze dependencies, scan locally, configure and query Sonar, and produce a consolidated pass/fail report. Minor gaps exist (e.g. no dedicated tool to fix or auto-remediate skill structure issues, no cross-skill content search), but core workflows have no dead ends.