Skip to main content
Glama
Fredo QA Skills MCP Server

Fredo QA Skills MCP Server

by illicomedia

Related Servers

Alternatives to Fredo QA Skills MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.
      13
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage, search, plan, and execute reusable skills while automatically enforcing always-on coding and reasoning guidelines. It provides workflow orchestration, permission-controlled execution, dynamic skill registration, and feedback-based ranking.
      9
      14 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides a quality framework and enforceable conventions for AI coding assistants, ensuring code quality, environment hygiene, and project standards across multiple AI tools.
      83 npm
      3
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables agents to pre-flight scan code or files, query paired anti-pattern and verified-fix examples, evolve and self-verify new guardrails from failure traces, and recompile portable skills and instructions for coding agents.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to enforce spec-driven development and verify code before it is marked done, using six tools that catch invented APIs, scan for hallucinated content, check plugin conformance, sandbox-run tests, validate schemas, and record audit evidence.
      771 npm
      8
      PolyForm Noncommercial 1.0.0

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target a distinct action: list_skills (enumerate), get_skill_rules (read one skill's SKILL.md), install_skill (single install), sync_workspace_skills (bulk auto-provision), prune_skills (archive). The main friction is install_skill vs sync_workspace_skills, and quick_check vs sync_workspace_skills, both of which detect project stack; descriptions differentiate them, but an agent could still hesitate over which provisioning path to pick.

    Naming Consistency4/5

    Eight of nine tools follow a clean verb_noun snake_case pattern (list_skills, get_skill_rules, install_skill, set_license_key, verify_license, get_version). The one deviation is quick_check, which is adjective_noun rather than verb-led, a minor inconsistency in an otherwise predictable scheme.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each earns its place across the three sub-domains (skill inventory/provisioning, licensing, preflight audit, version metadata). No filler or redundant tools inflate the surface.

    Completeness4/5

    The skill lifecycle is largely covered: list, read rules, install, bulk sync, and prune (non-destructive removal), plus license set/verify and version info. Minor gaps remain — no explicit uninstall/disable, no skill update or authoring path, and no way to filter skills by tier/category in list_skills — but agents can work around these via prune and list_skills.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues