Skip to main content
Glama
hostproof-mcp

hostproof-mcp

by DeveshB-1

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPRINTO_REGIONNoSprinto region to target; one of us, eu, in or au.us
HOSTPROOF_KUBECTLNoThe kubectl command to use for the Kubernetes cluster checks.kubectl
SPRINTO_API_TOKENYesYour Sprinto Developer API key, used to authenticate calls to Sprinto's Upload Evidence API and monitor lookup.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_checksA

List every check with its SOC 2 and ISO 27001:2022 control mapping.

run_compliance_checksA

Run read-only checks on this host (and the cluster, if include_k8s) and return pass/fail per check with the raw evidence behind each verdict.

write_evidence_bundleB

Run checks and write a zip (summary.md, results.json, raw/*.txt, sha256 manifest) to path.

list_sprinto_monitorsA

List monitors in the Sprinto workspace (pk, name, monitorType) to choose an upload target.

upload_evidenceA

Run the given checks, bundle them, and upload the zip to a Sprinto monitor. Without confirm=true this only returns a preview; show it to the user first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues