fleetalert-mcp
Related Servers
Alternatives to fleetalert-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to run allowlisted fleet SQL analytics, search synthetic policies, and submit ticket proposals for separate human approval, with role-based access, audit trails, and rate limits.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.MIT
- AlicenseNot gradedqualityCmaintenanceEnables production-hardened MCP tool serving with OAuth 2.1 audience-restricted tokens, purpose-bound tools, human-in-the-loop approvals, containment, and audit trails for AI agents.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search policies, look up bookings, list activities, create booking requests, issue or approve credits, and review audit records under role-based access. It enforces tenant isolation, filters fields by role, strips planted instructions from tool results, rate-limits each key, and writes tamper-evident audit logs.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Production Master incident-investigation service, enabling any MCP client to drive investigations via tool calls with pass-through authentication.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as editors to start and monitor missions, run the self-healing demo, list departments and blueprints, and approve tasks through the backend API. It also lets trusted departments discover and invoke explicitly granted external stdio or Streamable HTTP tools.1MIT
TDQS
Scored across 6 tools
The tools mostly target distinct needs: usage, alert listing, single alert summary, trace history, raw spans, and cross-alert activity. The main potential overlap is between get_trace and get_raw_spans, but the descriptions explicitly distinguish them by detail level and recommend get_trace by default.
All tools follow a clear verb_noun convention using get_ or list_ prefixes. The naming is predictable and readable throughout.
Six tools is well-scoped for an alert inspection/observability server. Each tool covers a distinct layer of information without excessive surface area.
Read-only inspection is well covered: alerts, investigation traces, raw spans, activity, and usage. However, the alert lifecycle includes statuses and human actions such as confirm/reject/resolve, but there are no action tools to mutate or progress an alert, which is a notable gap for the stated domain.