tibet-pol-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tibet-pol-mcprun health check on my_stack"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcpRelated MCP server: Trestle MCP
Claude Code / Claude Desktop Config
{
"mcpServers": {
"pol": {
"command": "tibet-pol-mcp",
"env": {
"TIBET_POL_TEMPLATES": "/path/to/your/templates"
}
}
}
}Available Tools
Tool | Description |
| Run health check against a template |
| List available check templates |
| Get template details and steps |
| Compare two runs — track infrastructure drift |
| Generate HTML report from results |
| 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 |
| Check passed |
| Was passing, now failing (state change) |
| Check failed |
| Dependency failed, step skipped |
| 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-fixIntents: 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 |
|
| 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
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Humotica/tibet-pol-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server