Scores code against a repo's own incident history, rolled into an 8 index Production Reliability Index (PRI). Exposes suggest_code, save_recommendation, and get_scan_report as tools.
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 8 tools
Most tools have clearly distinct purposes (scan, report, PR scoring, recommendation handling). However, get_tickets vs get_zendesk_tickets both fetch tickets, and get_dashboard_analytics vs get_support_agent_data both retrieve user-scoped page data with some metric overlap, creating mild potential for misselection.
All eight tools follow a consistent snake_case verb_noun pattern (get_*, save_*, score_*, suggest_*). No mixing of conventions or vague verbs.
Eight tools is well-scoped for a code scanning and support platform, covering the core workflow (scan, report, accept/reject, PR score, data fetch) without redundancy or bloat.
Core lifecycle is covered: suggest_code initiates a scan, save_recommendation accepts/rejects, get_scan_report retrieves the report, and score_pull_request handles PRs. Minor gaps exist (no tool to list historical scans by UUID, and tickets are read-only with no create/update/close operations).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_dashboard_analyticsget_scan_reportget_support_agent_dataget_ticketsget_zendesk_ticketssave_recommendationscore_pull_requestsuggest_code
Add one secure layer between your agents and this server.