Skip to main content
Glama
Presh-AR

codescan-mcp-server

by Presh-AR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to codescan-mcp-server

No user-submitted related servers found.

    Related Servers

    • sonarqube-mcp

      mshegolev
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for SonarQube that enables LLM agents to discover projects, analyze code quality metrics, check Quality Gate status, search issues with filters, and rank projects by worst-performing metrics. It provides read-only, safe access to SonarQube instances with structured outputs and error handling.
      5
      51 PyPI
      MIT

    • sonarqube-mcp

      metalralf
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that exposes SonarQube data as AI agent tools, enabling project discovery, quality gates, measures, issues, hotspots, rule explanations, source code, and raw API access.
      4
      -

    • sonarqube-mcp-py

      filhocf
      A
      license
      C
      quality
      D
      maintenance
      A Python MCP server for SonarQube, enabling AI agents to query projects, issues, quality gates, coverage, and security hotspots.
      13
      MIT

    • code-pathfinder

      shivasurya
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI coding assistants with access to call graphs, data flows, and security analysis for multi-file vulnerability detection.
      139
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing projects, retrieving issues for a project, and fetching metrics. There is no overlap or ambiguity.

    Naming Consistency4/5

    All tool names are single nouns, which is consistent. Adding verbs (e.g., list_projects) would make them more descriptive, but the pattern is uniform.

    Tool Count4/5

    3 tools is a reasonable number for a focused code scanning server. It covers the core actions without being overly sparse.

    Completeness3/5

    The server covers listing projects, retrieving issues, and getting metrics. Missing are details on individual projects, issue filtering, or update/delete operations, but for a read-only scanner it is fairly complete.

    Resources