tibet-pol-mcp
Related Servers
Alternatives to tibet-pol-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.2292 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for tibet-triage — process triage, flare rescue & reproducibility bundles with TIBET provenance.MIT
- AlicenseAqualityCmaintenanceAn MCP server for auditing automation health, finding failures, stale logs, and non-functional endpoints that report success while quietly failing.7MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to search, fetch, and analyze a self-maintaining markdown knowledge base with provenance, drift detection, and canonical definitions.1MIT
- AlicenseAqualityCmaintenanceArchitecture governance MCP server for AI-built codebases, enabling health checks, template management, and project scaffolding with migration support.511 npmMIT
- AlicenseAqualityAmaintenanceMCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.46 npmMIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: running full checks, quick health summaries, comparing results, generating HTML reports, viewing template details, and listing templates. The only similar pair is pol_check and pol_quick_health, but the latter is explicitly a simplified subset, so no ambiguity.
All tools follow the consistent pattern 'pol_<descriptive_name>', using lowercase with underscores (snake_case). The verbs and nouns are clear and predictable (check, diff, quick_health, report, template_info, templates).
With 6 tools, the count is well-scoped for a process checking server. Each tool serves a distinct function without being redundant or excessive.
The tool surface covers the full workflow: running checks (full and quick), comparing runs, generating reports, and exploring templates. There are no obvious missing operations for the server's stated purpose of process integrity verification.