phylax-mcp
OfficialRelated Servers
Alternatives to phylax-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for verification and API-existence oracle tools, enabling AI agents to check package existence, symbol details, and version diffs with signed attestations.9MIT
- AlicenseNot gradedqualityBmaintenanceA continuous, out-of-band trust and reliability layer for the MCP ecosystem. It fingerprints MCP server tool definitions, detects and classifies drift (e.g., rug pulls) via a severity taxonomy, maintains a hash-chained evidence ledger, and gates CI with SARIF—while also acting as an MCP server itself so agents can check a server's safety before binding.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for checking supply-chain trust before connecting to AI agents, frameworks, or MCP servers.839 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for tracking and verifying AI reasoning state, with signed action receipts, repo-history records, and preflight gating for tool calls.Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that provides tools for certificate verification, equivalence proving, and pre-registration sealing, enabling AI agents to re-derive verdicts from artifacts rather than trust assertions.9Apache 2.0
- FlicenseAqualityDmaintenancePackage intelligence MCP server. Stops AI agents from installing hallucinated/malicious packages across 17 ecosystems. 22 tools, free, no auth.221-
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of the verification workflow: single vs batch verification, MCP servers, attestations, policy checks, search, and status. Even verify_artifact and verify_artifacts are clearly delineated by cardinality with explicit guidance on when to use each.
The majority use a clear verb_noun pattern (verify_*, get_*, check_*, search_*). The singular phylax_status breaks the pattern by using a noun_verb structure, though it is still readable and not confusing.
At seven tools, the set is well-scoped for a verification service without redundancy or bloat. Each tool addresses a distinct need, and the batch variant is a justified convenience rather than a duplicate.
The core workflow (search, verify, attest, policy-check, status) is well covered. A minor gap is that check_policy handles only artifacts, not MCP servers, so policy evaluation for MCP server permissions is not explicit.