Skip to main content
Glama

Server Details

MCP gateway with 10 tools for code analysis, architecture, package audit & security.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes: audit_headers targets live URLs, check_package targets registry packages, check_test targets test suites, find_code/read_code target code search/reading, get_project_context targets project metadata, project_memory stores notes, Zephex_dev_info provides dev playbooks. Some potential confusion exists between find_code and read_code (both code-related) and get_project_context vs explain_architecture (both project overview-ish), but descriptions draw clear boundaries.

Naming Consistency4/5

Most tools follow a verb_noun pattern: audit_headers, check_package, check_test, find_code, read_code, get_project_context, project_memory. Deviations: keep_thinking (verb_gerund), explain_architecture (verb_noun but no underscore), and Zephex_dev_info (brand prefix, not verb_noun). Mostly consistent with a few outliers.

Tool Count5/5

10 tools is well within the ideal 3-15 range. Each tool covers a distinct capability area: URL auditing, package checking, test running, architecture mapping, code search, project context, structured thinking, memory, code reading, and dev playbooks. No tool feels redundant or unnecessary.

Completeness4/5

The tool surface covers a coherent developer-assistant workflow: understand project (get_project_context), search/read code (find_code, read_code), test (check_test), verify dependencies (check_package), audit deployed URLs (audit_headers), get expert guidance (Zephex_dev_info), and persist knowledge (project_memory). Minor gaps: no tool for editing/writing files, no direct deployment tool, and no explicit tool for running arbitrary commands, but these may be intentionally outside scope.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP gateway adding per-tool RBAC, tenant isolation, audit export, and PII redaction to any server.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP gateway and control plane that aggregates and manages MCP servers and tools, providing unified access, a web console, access control, invocation auditing, and integrated build/deploy workflows.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP gateway that lets MCP clients connect once and then discover and execute tools across multiple MCP servers, with centralized credential management, per-tool access control, CLI, and dashboard.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources