Skip to main content
Glama
malinoto

tracepass-mcp-server

by malinoto

Related Servers

Alternatives to tracepass-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for embedding and verifying C2PA content credentials (provenance) in AI-generated assets, with HMAC-based tamper-evident manifests and optional X.509 support, helping comply with EU AI Act Article 50.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Tamper-evident audit trail MCP server for EU AI Act and GDPR compliance. It enables logging events with automatic PII scanning, compliance checks, and right-to-erasure support.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for French Electronic Invoicing (NF XP Z12-013). Provide tools to validate, generate, and explore API specifications for PDP/OD interoperability.
      2
      34
      Apache 2.0

    TDQS

    A4.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct resource domain: passports, fields, parties, products, templates, and EPCIS events. An agent can unambiguously pick the right tool for a given resource, and the action parameter further separates operations within each tool.

    Naming Consistency4/5

    All six tools share a consistent `tracepass_` prefix and snake_case noun convention (tracepass_passports, tracepass_products, tracepass_epcis). Minor inconsistency: some use singular nouns (tracepass_epcis, tracepass_templates) while others are plural/compound (tracepass_passport_fields, tracepass_passport_parties), but the pattern is still predictable.

    Tool Count5/5

    Six well-scoped tools, each representing a coherent domain that groups related actions via the `action` parameter rather than exploding into dozens of separate tools. This is an efficient, appropriate granularity for the breadth of the DPP lifecycle.

    Completeness4/5

    The surface covers the full passport lifecycle (create/list/get/suspend/archive), field edits, parties, products, templates, EPCIS events, measurements, condition flags, and snapshots. Minor gap: snapshots expose `restorable` but there is no restore action, and there is no explicit delete for products/passports (soft-archive only), though that appears intentional.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues