clearon-ops-audit-mcp
Related Servers
Alternatives to clearon-ops-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRead-only MCP tools for coding agents to audit deployment targets, detect fabricated code, review backlog, database schema, analytics, ML models, architecture docs, and decision lenses.117 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only production observability through a small set of tools for health, job status, latest data, approved logs, and deployment metadata, enabling AI planning and review without a production write path.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to audit server health and operations through read-only tools, including container status, logs, alerts, and WhatsApp session status, without requiring SSH access.-
- AlicenseNot gradedqualityCmaintenanceEnables authorized security auditing of AI-agent supply chains and agent-facing surfaces: deterministic local skill-bundle audits against eight attack patterns, secrets scanning, and scope-gated read-only recon of agent endpoints and MCP surfaces.MIT
- AlicenseNot gradedqualityCmaintenanceEnables approved senior engineers to run vetted, read-only audit scripts on Tactical RMM agents from Claude, using a fixed catalog of tools to inspect things like local admins, disk space, and installed software without permitting arbitrary code execution or destructive actions.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect and audit Azure Landing Zones by inventorying resources, auditing tagging, evaluating policy compliance, and detecting infrastructure drift, all in read-only mode.-
TDQS
Scored across 11 tools
Several tools cluster around health and failure detection—get_server_health/check_gateway_health/probe_registered_mcps overlap in probing MCP/gateway state, and get_recent_failures/check_delivery_failures/find_missed_or_overdue_runs all surface different failure modes. Descriptions clarify the distinctions, but an agent could misroute a health/failure query without careful reading.
All tool names are snake_case and mostly follow a verb_noun pattern, but verb choices are inconsistent: get/list/find/summarize/probe/check/audit/generate are used interchangeably, and check_/get_ overlap semantically. Still readable and object-focused.
11 tools is well within the sweet spot for a specialized read-only ops audit server. Each tool corresponds to a distinct audit concern (health, jobs, failures, MCPs, delivery, locks, reporting) without bloat.
The surface covers the main read-only audit workflow: enumerate jobs, assess job/server/gateway health, surface failures and anomalies, audit locks, and generate a report. Minor gaps like per-tool historical trend endpoints or more granular failure detail are workaround-able.