MCP server for tibet-pol — machine & process health monitoring with TIBET provenance
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tibet-pol-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# tibet-pol-mcp **MCP server for tibet-pol — machine & process health monitoring with TIBET provenance.** Run infrastructure integrity checks via JSON templates. Every step is verified, dependency-chained, and signed with [TIBET](https://datatracker.ietf.org/doc/draft-vandemeent-tibet/) tokens. Like htop meets audit trail. Part of the [TIBET ecosystem](https://humotica.com) by [HumoticaOS](https://github.com/Humotica). ## Install ```bash pip install tibet-pol-mcp ``` ## Claude Code / Claude Desktop Config ```json { "mcpServers": { "pol": { "command": "tibet-pol-mcp", "env": { "TIBET_POL_TEMPLATES": "/path/to/your/templates" } } } } ``` ## Available Tools | Tool | Description | |------|-------------| | `pol_check` | Run health check against a template | | `pol_templates` | List available check templates | | `pol_template_info` | Get template details and steps | | `pol_diff` | Compare two runs — track infrastructure drift | | `pol_report` | Generate HTML report from results | | `pol_quick_health` | One-shot health percentage + failed steps | ## How It Works Define infrastructure checks as JSON templates: ```json { "process_id": "my_stack", "name": "My Infrastructure", "steps": [ { "id": "api_health", "name": "API responds", "check": "curl -sf http://localhost:8000/health", "critical": true, "intent": "Core API must be reachable" }, { "id": "db_connected", "name": "Database connection", "check": "pg_isready -h localhost", "dependencies": ["api_health"], "critical": true } ] } ``` Then check via MCP: ```python pol_check("my_stack") # → 100% health, all steps valid, TIBET token chain pol_quick_health("my_stack") # → {"health": "100%", "checksum": "2/2", "failed_steps": []} ``` ## Step Statuses | Status | Meaning | |--------|---------| | `valid` | Check passed | | `drift` | Was passing, now failing (state change) | | `broken` | Check …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.