ghost-audit-mcp
Related Servers
Alternatives to ghost-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceRead-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
- FlicenseNot gradedqualityDmaintenanceEnables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.-
- AlicenseNot gradedqualityCmaintenanceProvides read-only MCP tools for market snapshots, position risk, order reconciliation, and daily report previews with deterministic financial calculations, evidence chains, and audit trails.MIT
- AlicenseBqualityBmaintenanceEnables read-only visibility into management status, assets, alerts, events, policies, reports, roles, users, and syslog through governed MCP and CLI calls. Credentials stay in environment variables, TLS verification remains on, and each call records a local audit event.35MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agent hosts to delegate governed, read-only security audits and reviews of code, applications, agents, prompts, MCP configurations, and cloud environments through evidence-first findings and stable schemas.2Apache 2.0
- AlicenseAqualityBmaintenanceEnables read-only lookup and analysis of SaaS applications, transactions, invoices, spend, renewals, and people, including spend summaries, upcoming renewals, and missing-invoice checks, through an MCP client.7MIT
TDQS
Scored across 10 tools
Each tool targets a distinct task: describe (glossary), summary (portfolio), list_cases (filter rows), get_case (full case context), explain_case (narrative with citations), get_evidence (file metadata/snippet), review_queue (human queue), whatif (re-run simulation), ingest_report (ingestion diagnostics), verify_output (contract validation). The read-side case tools (list/get/explain) operate at clearly different granularity and the descriptions even guide sequencing ('Use before ghost_get_case').
All names share the consistent 'ghost_' prefix and snake_case convention, which is good. Most are verb_noun (get_case, list_cases, explain_case, verify_output, ingest_report), but a few are noun/other-style (summary, review_queue, whatif), a minor deviation from a strict pattern.
Ten tools is well within the ideal range and each earns its place: reporting, per-case inspection, evidence access, review, simulation, ingestion, and validation are all non-redundant functions. No filler tools present.
The audit/verification lifecycle is well covered: ingestion diagnostics, portfolio summary, case listing/inspection/explanations, evidence, review queue, what-if simulation, and output validation. Minor gaps exist—no tool to retrieve full evidence content (binaries intentionally withheld) and no write/resolve action for review items, but these reflect deliberate read-only design.