hostproof-mcp
Related Servers
Alternatives to hostproof-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI clients to collect read-only confidentiality evidence from registered Linux, WSL, and Docker targets, walk through ten ISO-aligned hardening steps, and generate professional audit reports. It also builds reviewable remediation plans and verifies supported changes with rollback and after-evidence when writes are explicitly enabled.9MIT
- AlicenseAqualityDmaintenanceEnables AI agents to query SOC 2 and ISO 27001 control evidence with server-enforced authorization, including scoped access, column masking, and audit logging.8MIT
- AlicenseBqualityCmaintenanceEnables MCP-compatible agents to perform read-only incident investigations by querying logs, building timelines, searching runbooks, validating evidence, and creating ticket drafts only with explicit approval.7MIT
- AlicenseBqualityBmaintenanceEnables read-only inspection of local Windows and Linux systems for host, resource, network, service, software, identity, startup, certificate, SSH key metadata, and environment-variable name evidence through MCP tools. It normalizes platform outputs into stable schemas while avoiding arbitrary shell execution, credential reads, secret values, or remediation.23MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables LLMs and AI agents to perform defensive security posture assessments, privilege escalation surface audits, and post-quantum cryptography readiness checks through read-only diagnostic tools.MIT
TDQS
Scored across 5 tools
The three execution tools share a 'runs checks' behavior, so an agent must read carefully to pick between run_compliance_checks (return results inline), write_evidence_bundle (write zip locally), and upload_evidence (bundle + push to Sprinto). The names do signal distinct terminal actions (run/write/upload), which keeps selection mostly clear, though the overlap in underlying behavior creates some risk of misselection.
All five tools follow a strict snake_case verb_noun pattern: list_checks, run_compliance_checks, write_evidence_bundle, list_sprinto_monitors, upload_evidence. The convention is predictable and readable throughout.
Five tools is well-scoped for a host compliance-evidence server: enumerate checks, execute them, produce a bundle, discover upload targets, and upload. Each tool maps to a distinct step in that workflow with no obviously redundant surface.
The core lifecycle is covered end to end: discover checks and their control mappings, run them, package evidence, list monitors, and upload. Minor gaps remain, such as inspecting a single check's detail, filtering runs by control or check subset, or verifying/fetching previously uploaded evidence, but agents can work around these.