tracepass-mcp-server
Related Servers
Alternatives to tracepass-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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
- AlicenseAqualityBmaintenanceMCP server for GoCertius: certified evidence, dossiers, notifications and chats via AI agents.4175 npmMIT
- AlicenseNot gradedqualityDmaintenanceTamper-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
- AlicenseAqualityBmaintenanceModel 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.341Apache 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 9 tools
The nine top-level tools map to largely distinct TracePass domains: products, passports, lifecycle operations, access grants, EPCIS, field updates, parties, scope, and templates. Some care is needed to distinguish registry-preparation actions inside `tracepass_passports` from registration/lifecycle actions in `tracepass_passport_lifecycle`, and passport field edits from passport creation, but the descriptions make these boundaries workable.
All tool names use the same `tracepass_` prefix, snake_case formatting, and resource-noun pattern. Action names within tools are also consistently verb-like and predictable; minor singular/acronym differences like `tracepass_scope` and `tracepass_epcis` do not disrupt the pattern.
Nine top-level tools is a well-scoped count for a broad DPP platform. Each tool corresponds to a meaningful resource or workflow area, even though `tracepass_passports` is action-heavy and must expose many related operations.
Coverage is very comprehensive: product catalogue management, passport creation/read/compliance/registry readiness, lifecycle transitions, access grants, EPCIS capture/query/export, field and party updates, scope checks, and templates. Publishing appears intentionally dashboard-only rather than missing, and I see no major dead ends in the core domain.