proxy-aiops
Related Servers
Alternatives to proxy-aiops
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceGoverned Prometheus + Grafana operations — firing-alert and scrape-target RCA, alert noise/flapping analysis, silences, and dashboards, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.39MIT
- AlicenseAqualityAmaintenanceGoverned Docker + Portainer container-host operations (non-Kubernetes) — restart-loop, resource-pressure, and image/volume-bloat RCA, with guarded lifecycle writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.38MIT
- AlicenseAqualityAmaintenanceGoverned CI/CD operations for self-hosted GitLab and Gitea — pipeline-failure, runner, artifact-bloat, and stale-branch RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.28MIT
- AlicenseAqualityAmaintenanceGoverned OPNsense + pfSense firewall operations — gateway-health, rule-shadow, and blocked-traffic RCA, with guarded rule/alias writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.351MIT
- AlicenseAqualityAmaintenanceGoverned SSO/IAM operations for Keycloak and Authentik — login-failure, stale-permission, client-config, and MFA RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.29MIT
- AlicenseAqualityBmaintenanceSecurity, cost, and health governance proxy for MCP infrastructure. Enforces YAML-configurable security policies (blocklists, rate limits, token budgets), tracks real token costs via tiktoken, monitors server health with live JSON-RPC probes. Features OAuth 2.1/OIDC with RBAC, web dashboard, payload normalization, semantic shell AST analysis, mTLS, and a formal STRIDE threat model.459 npm4MIT
TDQS
Scored across 28 tools
Most tools target a distinct resource+action, and the raw-list vs RCA-analysis pattern is consistent. However, pairs like list_certificates/cert_expiry_sweep and traffic_stats/error_counters overlap enough that an agent may need to read descriptions to choose.
All names use snake_case and follow recognizable patterns (list_X, X_detail, set_X, *_rca). Some tools are noun phrases rather than verb_noun (config_snapshot, route_conflict_analysis, undo_apply), so the convention is mostly but not perfectly consistent.
28 tools is heavy for one server, and several granular list/detail pairs plus platform-specific wrappers inflate the surface. Each tool maps to a real operation, but consolidation would improve usability, making this borderline rather than well-scoped.
The surface covers broad proxy diagnostics (health, config, certs, routes, errors, traffic) and includes caddy config writes and haproxy server controls with undo. Gaps remain: no log/restart/reload tools, no traefik config writes, and certificate renewal is only hinted at rather than actionable.