A
licenseNot graded
qualityD
maintenanceZero-dependency MCP server inspector for protocol conformance, tool annotations, and capability checks.
MIT
monitor
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
- 92.2% over 76 days
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
3 tool updates
- First observed
check_mcp_server - First observed
get_drift_feed - First observed
get_findings
Related MCP Connectors
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.
Security research: MCP registries verify identity, not tool behavior. See gtfo.dev.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceScans MCP servers for deprecated and removed protocol features, providing a dated migration checklist.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server inspector that reads a server's published source code and reports findings with file:line evidence, helping users assess what an MCP server does before connecting.MIT
- AlicenseNot gradedqualityBmaintenanceZero-execution static AST security scanner and vulnerability auditor for MCP servers. Detects Command Injection (CWE-78), Path Traversal (CWE-22), Hardcoded Secrets (CWE-798), and Unauthenticated Transports (CWE-306).MIT
Try in Browser
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
Glama MCP Gateway
Add one secure layer between your agents and this server.