Skip to main content
Glama

Server Details

Check if an MCP server tool changed or hides injection patterns before you trust it.

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

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: check_mcp_server targets a single server for both changes and injection patterns, get_drift_feed scans the ecosystem for recently changed tools, and get_findings lists tools with detected patterns. No two tools are likely to be confused.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: check_mcp_server, get_drift_feed, get_findings. The verbs 'check' and 'get' are both action-oriented and appropriate, maintaining predictable naming.

Tool Count4/5

Three tools is a compact but reasonable set for a monitoring server focused on MCP ecosystem changes and security. While slightly lean, each tool covers a core concern without redundancy.

Completeness4/5

The surface covers the primary monitoring actions: checking a specific server, browsing ecosystem drift, and retrieving findings. A minor gap is the lack of a detailed drill-down for why a specific server is flagged beyond the initial verdict, but workflows are still functional.

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

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources