tracepass-mcp-server
Related Servers
Alternatives to tracepass-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP 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
- AlicenseAqualityAmaintenanceMCP server for GoCertius: certified evidence, dossiers, notifications and chats via AI agents.4183 npmMIT
- AlicenseNot gradedqualityCmaintenanceTamper-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
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT
- AlicenseAqualityAmaintenanceModel 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.234Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA hosted remote MCP server for verifying C2PA intakes, classifying source risk, issuing media receipts, and exporting intake logs. Designed for AI governance, trust and safety, and compliance teams.MIT
TDQS
Scored across 6 tools
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.
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.
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.
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.