Skip to main content
Glama
PhpCodeArcheology

PhpCodeArcheology

Official
by PhpCodeArcheology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to PhpCodeArcheology

No user-submitted related servers found.

    Related Servers

    • Tech Debt MCP Server

      PierreJanineh
      A
      license
      A
      quality
      B
      maintenance
      A server for analyzing technical debt across multiple programming languages, integrating with MCP-compatible tools to detect code quality issues and provide prioritized recommendations.
      16
      76 npm
      7
      MIT

    • arch-optimize

      bfxh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides tools for architecture analysis, risk diagnosis, quality metrics, and regression guarding to support AI-driven code review and incremental refactoring workflows.
      5
      MIT

    • trace-mcp

      nikolai-vysotskyi
      A
      license
      A
      quality
      A
      maintenance
      Framework-aware code intelligence MCP server that builds a cross-language dependency graph from source code. 53 integrations (Laravel, Django, Rails, Spring, NestJS, Next.js, and more) across 68 languages. 100+ tools for navigation, impact analysis, refactoring, security scanning, session memory, and CI/PR reports — up to 97% token reduction.
      29
      1,663 npm
      176
      MIT

    • Repo Therapist

      salman-arefin74
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that transforms repositories into queryable knowledge by combining static code analysis with git history tracking. It allows users to investigate codebase structure, identify fragile files based on churn, and receive risk assessments through natural language queries.
      7
      -
    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.5/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target a clear, distinct slice of project analysis—health, problems, dependencies, impact, coverage, hotspots—so an agent can usually pick correctly. A few pairs overlap somewhat (get_class_list vs get_refactoring_priorities, get_metrics vs get_class_list), but the descriptions provide enough differentiation.

    Naming Consistency5/5

    All tools follow the `get_` or `search_` prefix with lowercase snake_case nouns, creating a highly predictable pattern. The naming clearly communicates read-only analysis operations consistent with the server's purpose.

    Tool Count5/5

    Eleven tools is well within the ideal range for a code-analysis server. Each tool covers a meaningful analysis concern without redundancy or bloat.

    Completeness5/5

    The surface covers the full archeology workflow: overall health, problems, refactoring priorities, class metrics, dependencies, graph navigation, search, impact analysis, test coverage, and hotspots. For a read-only analysis tool, there are no obvious dead ends or missing core capabilities.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources