Skip to main content
Glama
Malkovsky

ce-analyzer-mcp

by Malkovsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ce-analyzer-mcp

Related Servers

  • clangd-mcp

    ibuildrun
    A
    license
    A
    quality
    D
    maintenance
    MCP server for C/C++ code analysis using clangd and clang tools, providing diagnostics, symbol search, include analysis, function listing, and code formatting.
    5
    MIT

  • dejared-mcp

    hqkh4nh
    A
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server for exploring, analyzing, and decompiling Java JAR files.
    148 npm
    5
    MIT

  • code-intel

    team-harness
    A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.
    22 npm
    2
    MIT

  • GeminiCLI MCP Antigravity

    wu55246842
    F
    license
    Not graded
    quality
    D
    maintenance
    A local MCP server for code analysis and investigation, providing tools like code search, file read, and symbol hint via SSE for integration with Gemini CLI and Antigravity.
    -

  • source-rag-mcp

    hanhy06
    F
    license
    B
    quality
    B
    maintenance
    MCP server for searching, browsing, and analyzing decompiled Minecraft source code locally. Supports symbol lookup, text search, reference lookup, and lightweight RAG.
    11
    -
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

A3.7/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource or action: searching for analyzers/compilers/libraries, compiling, comparing, analyzing, shortlink management, and opcode documentation. The search_* trio is clearly differentiated by query object, and compile/compare/analyze have non-overlapping purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern, with search_ prefix for discovery, action verbs for operations, and get_/create_ for shortlink/documentation. No mixed naming conventions or vague verbs.

Tool Count5/5

Nine tools provide a well-scoped set covering resource discovery, compilation, comparison, analysis, sharing, and documentation lookup. Each tool has a clear purpose within the domain, and the count is neither bloated nor thin.

Completeness4/5

The core workflow—discover resources, compile, compare, analyze, and share via shortlinks—is well covered. Minor gaps exist, such as library discovery not directly connecting to compilation configurations, and there is intentionally no delete shortlink operation, but these are not critical dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources