Skip to main content
Glama
Anselmoo

mcp-server-analyzer

by Anselmoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-server-analyzer

No user-submitted related servers found.

    Related Servers

    • python-mcp

      yriveiro
      A
      license
      A
      quality
      C
      maintenance
      This MCP server provides direct access to ruff linting, formatting checks, and ty type-checking for Python projects, with token-efficient, structured output.
      9
      MIT

    • ruff-mcp-server

      drewsonne
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that integrates Ruff linting, formatting, and code analysis tools with advanced logging and configuration options for AI coding assistants.
      4
      1
      MIT

    • codetest-mcp

      jihyun0410
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for static code analysis using AST parsing and linters, providing tools to detect syntax errors, type issues, typos, and incorrect variable usage across multiple languages. It supports headless linting with tools like ast_check, lint_check, and health.
      -

    • wemake-python-mcp

      guff192
      A
      license
      A
      quality
      B
      maintenance
      MCP server providing automated code linting, rule explanations, and configuration templates for wemake-python-styleguide, with structured violation reports and offline rule database.
      5
      MIT

    • code-ast-mcp

      m-sameerkhan
      A
      license
      A
      quality
      B
      maintenance
      This MCP server enables AI models to analyze local Python codebases using abstract syntax trees, providing tools for file structure analysis, symbol search, import graphing, docstring auditing, and refactoring prompts without loading entire source files into context.
      4
      5
      MIT
    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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are clearly distinct by language and action (format, lint, type-check, dead-code scan). The only real ambiguity is ruff-check vs. ruff-check-ci, which differ only in CI-specific output formatting.

    Naming Consistency4/5

    Names generally follow a consistent 'tool-action' hyphenated pattern (ruff-format, biome-check, vulture-scan). analyze-code breaks the pattern slightly by leading with the action rather than the tool.

    Tool Count4/5

    Eight tools is a reasonable size for a code-analysis server. The count is slightly padded by ruff-check-ci and the combined analyze-code, which overlap with existing tools, but the overall scope remains manageable.

    Completeness3/5

    Python coverage is strong: format, lint, type-check, dead-code, and a combined analysis. JavaScript/TypeScript support is thinner, with only formatting and linting and no type-checking or dead-code detection, leaving a notable gap for a general analyzer.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources