Skip to main content
Glama
TaskBounty Check

TaskBounty Check

Related Servers

Alternatives to TaskBounty Check

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Local repository health diagnosis and fix planning for AI-written JavaScript, TypeScript, Python and mixed projects. Its stdio MCP server exposes scans, finding explanations, repair plans, verification, privacy review and DPDP technical readiness checks.
      11 npm
      35
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables offline auditing of GitHub Actions workflows through MCP, surfacing security and correctness findings with exact file/line locations and fixes, explaining cron schedules, visualizing job dependencies, reviewing token permissions, planning commit-SHA pins, and previewing safe patches proven by re-linting.
      7
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Scans GitHub Actions workflow files for dangerous triggers, template injection, unpinned actions, excessive permissions, and secrets in shell commands before they are committed, exposing the checks as MCP tools for agents.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables auditing GitHub Actions workflows for security problems directly from an MCP client, returning a risk score and findings with file:line evidence, attack narratives, and fixes. Also exposes the full rule catalog and a one-call demo that writes and scans a deliberately broken workflow.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.
      70 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      CI health reports for GitHub Actions: flaky tests named from logs, wasted compute priced in dollars, zombie crons, PR feedback time, plus 21 lint rules with safe auto-fixes. Read-only MCP tools wrap the same Go binary.
      7
      3
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scanning produces findings, explaining interprets them, and generating a fix plan suggests steps. There is no overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (explain_finding, generate_fix_plan, scan_repo), making them predictable and easy to understand.

    Tool Count5/5

    With only 3 tools, the set is tightly scoped to a specific workflow (scan, explain, fix). This is appropriate for a focused server, avoiding unnecessary complexity.

    Completeness4/5

    The tools cover the main workflow from scanning to understanding to suggesting fixes. A minor gap is the lack of a tool to list all possible rules without scanning, but the workflow remains functional.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues