Skip to main content
Glama

Related Servers

Alternatives to topai-mcp-suite

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An enterprise-grade Model Context Protocol server that provides comprehensive GitHub repository analysis and AI-powered development assistance through 11 streamlined tools.
      11
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Model Context Protocol server for security research automation, integrating multiple security testing tools into LLM-driven workflows for secret scanning, static analysis, and vulnerability discovery.
      57
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Local-first code context CLI + MCP server: discover, index, and search repos; generate task-aware context packs, code maps, agent harnesses, and PR-review/merge-readiness gates for coding agents and reviewers.
      14
      428 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.
      8
      MIT

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a clearly distinct domain: AST pruning, PR/diff security, Dockerfile linting, IP classification, Terraform blast radius, 3D packing, flaky test analysis, SQL anonymization, and SEC filing parsing. Descriptions explicitly state when to use, when not to use, and alternatives, making misselection unlikely despite branded names.

    Naming Consistency4/5

    All names use snake_case and end with a clear action verb (trim, audit, lookup, evaluate, pack, analyze, anonymize, parse). The pattern is consistent, but opaque product/mechanism prefixes like tokenprune, agentpr, and edgarpulse reduce predictability from the domain alone.

    Tool Count5/5

    Nine tools is a well-scoped count for a utility suite, with no apparent filler or redundant operations. Each tool appears to earn its place as a distinct local analyzer.

    Completeness4/5

    Each tool provides a self-contained operation for its stated purpose, and the suite covers a broad set of engineering and data tasks. Minor gaps exist around composing outputs or applying remediation, but the read-only analyzer model does not require full CRUD lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues