Skip to main content
Glama
abyssbugg-labs

Sourcery MCP Server

Related Servers

Alternatives to Sourcery MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes six security tools (scan_repo, scan_diff, list_findings, get_finding, verify_finding, list_detectors) over stdio or HTTP so AI coding agents can run SAST/SCA/secrets/IaC scans and inspect prioritized findings without writing to the repository. It also lets agents verify a finding by re-running its generated proof-of-concept in an isolated sandbox, returning a confirmed or unavailable verdict.
      18
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Allows developers to query security findings (SAST issues, secrets, patches) using natural language within AI-assisted tools like Claude Desktop, Cursor, and other MCP-compatible environments.
      17
      10
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Agent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.
      1
      4 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to scan code for security vulnerabilities using multiple static analysis tools, with support for filtering, deduplication, and CI/CD integration.
      27
      57 PyPI
      4
      MIT

    TDQS

    B3/5.0

    Scored across 12 tools

    Disambiguation3/5

    Tools are organized around three distinct resources (findings, groups, counts) with clear actions, but there is overlap between sourcery_security_snapshot, sourcery_get_security_counts, and sourcery_get_group_counts, which could cause confusion about which to use for simple count retrieval. The compatibility bridge sourcery_api_request overlaps with all typed operations.

    Naming Consistency4/5

    Nearly all tools follow a consistent 'sourcery_verb_noun' pattern (list_findings, get_group, bulk_update_findings, build_fix_prompt). Slight inconsistency in 'security_snapshot' and 'api_request' which are nouns rather than verb_noun, but overall very predictable.

    Tool Count4/5

    12 tools is a reasonable number for a security finding management server. The presence of both typed tools and a generic API request bridge is slightly redundant but justified as a compatibility layer.

    Completeness4/5

    The server provides full lifecycle coverage for findings and groups (list, get, bulk update) and helpful aggregation tools. However, it lacks single-item update operations (only bulk), and does not support creating or deleting findings/groups, which may be by design but creates minor gaps for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues