Skip to main content
Glama
Karzone

TestAtlas

by Karzone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to TestAtlas

No user-submitted related servers found.

    Related Servers

    • Slnmap

      EMahmoudNabil
      A
      license
      Not graded
      quality
      B
      maintenance
      A semantic map of your .NET solution for AI coding agents. Analyzes a solution with Roslyn into a queryable code graph exposing 11 read-only tools (find_symbol, impact_analysis, find_implementations, etc.) over MCP. 100% local, no telemetry, MIT licensed.
      24
      MIT

    • CodeMap MCP

      bbajt
      F
      license
      Not graded
      quality
      B
      maintenance
      CodeMap is a Roslyn-powered MCP server that lets AI agents navigate C# codebases by symbol, call graph, and architectural fact, instead of brute-force reading thousands of lines of source code. One tool call. Precise answer. No context flood.
      20
      -

    • archiet-xray

      Anioko
      A
      license
      A
      quality
      C
      maintenance
      Extracts deterministic architecture maps from codebases for AI agents, enabling queries about blast radius, routes, security findings, and production readiness without sending code anywhere.
      6
      MIT

    • qa-mcp

      shahinnr
      A
      license
      A
      quality
      C
      maintenance
      Automated QA for .NET microservice backends and React frontends, enabling API contract testing, UI crawling, YAML flows, and run diffing against a stage environment.
      7
      11 npm
      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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation3/5

    Most tools are distinct, but several revolve around step definitions: search_steps, resolve_step, get_step_definition, and step_catalog all have overlapping surfaces and could cause misselection. impact and list_endpoints also share blast-radius concepts for endpoints. Descriptions help, but an agent may need to read carefully to pick the right tool.

    Naming Consistency3/5

    The tools mostly use verb_noun snake_case (search_steps, list_endpoints, get_scenario, list_tags), but several are bare nouns (stats, impact, step_catalog, project_dependencies). The mixed conventions are still readable, yet the pattern is not uniform.

    Tool Count5/5

    11 tools is well within the ideal scope for a test-suite analysis server. Each tool contributes a meaningful capability, from summary stats to step resolution to dependency analysis, and none feel redundant enough to cut.

    Completeness5/5

    For its apparent purpose—discovering, understanding, and safely reusing steps and scenarios in a test suite—the surface is thorough. It covers search, detailed lookup, resolution before authoring, impact analysis, endpoint visibility, tagging, a step catalog for composition, and project dependencies. There are no obvious dead ends or missing critical operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources