Skip to main content
Glama
praxi-labs

phylax-mcp

Official
by praxi-labs

Related Servers

Alternatives to phylax-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for verification and API-existence oracle tools, enabling AI agents to check package existence, symbol details, and version diffs with signed attestations.
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A 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
    • A
      license
      A
      quality
      A
      maintenance
      An 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.
      9
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues