clearon-ops-audit-mcp
Related Servers
Alternatives to clearon-ops-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceInspect a cronstable job scheduler's jobs, logs, run history, DAG workflows, and cluster health, and ask why a job did or didn't run. Read-only by default; tools that run, pause, or approve jobs and workflow runs need opt-in.19394 PyPI141MIT
- AlicenseBqualityAmaintenanceRead-only MCP server that exposes governed operational records with provenance and validity windows so clients can check which evidence is still current before answering. It lets agents reconcile freshness, schedule state, and evidence specificity to determine whether scheduled automations are actually healthy, rather than trusting an expired dashboard summary.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables secure, read-only-by-default inspection and auditing of load balancers, WAF, policies, bot defense, API security, security events, and logs, with planned human-confirmed writes for selected configuration changes and no deletions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables auditing key ceremonies, checking backup and verification status, and reviewing HSM configurations and firmware through MCP tools.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to deterministically audit claimed data-deletion requests, reconstruct what personal data remains reachable at a chosen cut-off, and retrieve evidence, case details, queues, what-if results, and verification outputs. It is read-only and lets agents build risk dashboards, review queues, case cards, and DPO briefs from the same capabilities as the CLI.10MIT
- AlicenseAqualityDmaintenanceRead-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.115 npmMIT
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.