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 tokens. Like htop meets audit trail.
Part of the TIBET ecosystem by HumoticaOS.
Install
pip install tibet-pol-mcp
Claude Code / Claude Desktop Config
{
"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:
{
"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:
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 failed |
blocked |
Dependency failed, step skipped |
pending |
Not yet checked |
Template Features
- Dependencies: Steps can depend on other steps (topological sort)
- Critical flags: Critical failures block dependent steps
- Remediation:
on_failurecommands for auto-fix - Intents: Document WHY each check exists
- Success criteria: Min percentage, all-critical rules
- Alerts: Commands on critical failure or threshold breach
Environment Variables
| Variable | Default | Description |
|---|---|---|
TIBET_POL_TEMPLATES |
/srv/jtel-stack/tibet-pol-processes |
Templates directory |
Related TIBET Packages
tibet-audit— Core TIBET provenancetibet-pol— CLI/Python API (dependency)tibet-triage-mcp— Process triage MCP servertibet-phantom-mcp— Cross-device AI sessionstibet-ipoll-mcp— AI-to-AI messaging
License
MIT — HumoticaOS
Metadata
Release files for tibet-pol-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tibet_pol_mcp-0.1.0.tar.gz | 5.9 kB | Without provenance | Details for tibet_pol_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tibet_pol_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for tibet_pol_mcp-0.1.0-py3-none-any.whl |
Total release size: 13.1 kB
Release files / tibet_pol_mcp-0.1.0.tar.gz
| Download URL | tibet_pol_mcp-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5853b6b950dcb344d2826634050068ca47af4c85b4926f401455335463703e5a
|
|
BLAKE2b-256 checksum How to use checksums |
e4ece9afc9bd97f6d0ba710d823fc3eafc03ee7d60bb1bdb13d24a6d75efc4df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / tibet_pol_mcp-0.1.0-py3-none-any.whl
| Download URL | tibet_pol_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30bcbe782aac7abf423f44979f61714d00d645d61cf5b1c97509d1427c27f683
|
|
BLAKE2b-256 checksum How to use checksums |
e18c3dacd1c6e827b24fdabddaee1484315c7d907709d9fb1479fbf70e928688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for tibet-pol-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.