MCP-native AI SRE. Exposes your production OpenTelemetry problems, traces, and logs over the Model Context Protocol, plus an AI remediation loop that opens a reviewed GitHub fix PR and verifies in production (reopening on regression). Tools include list_problems, get_problem, query_traces, detect_anomalies, and request_problem_remediation. Human-in-the-loop by default — the merge button stays yours.
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.
Scored across 2 tools
signup and verify_email have clearly distinct roles: one initiates the email code flow, the other consumes the code to produce a token. There is no overlap or ambiguity between them.
Both names are lowercase and imperative, but signup is a single-word verb while verify_email follows a verb_noun pattern. The naming is predictable and readable despite the minor inconsistency.
Two tools make sense for a minimal email-code auth flow, but the set feels thin because the descriptions reference additional onboarding tools that are not exposed. It sits at the borderline of being too few.
The pair covers code request and verification, but verify_email instructs the agent to call verify_connection and get_activation_status to finish onboarding, and neither tool exists in this server. This creates a significant gap where the intended workflow cannot be completed.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
signupverify_email
Add one secure layer between your agents and this server.