AI BOM MCP
Related Servers
Alternatives to AI BOM MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceScans codebases for AI frameworks, checks EU AI Act compliance, and generates compliance reports, roadmaps, and audit-ready packages.1611MIT
- FlicenseNot gradedqualityNot gradedmaintenanceOpen-source AI governance toolkit. MCP servers & CLIs for scanning, auditing, and managing your AI environment-
- AlicenseNot gradedqualityNot gradedmaintenanceOpen-source AI governance toolkit — MCP servers & CLIs for scanning, auditing, and managing your AI environment1-
- AlicenseAqualityDmaintenanceScans codebases for AI system usage and generates EU AI Act compliance reports.435 npmMIT
- AlicenseNot gradedqualityCmaintenanceGenerates SBOM in CycloneDX 1.6 and SPDX 2.3 formats, compliant with EO 14028, NIS2, and CRA.23 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first AI compliance scanner via Model Context Protocol, scanning codebases for violations of DPDPA 2023, RBI FREE-AI, SEBI AI/ML, and the EU AI Act.27 PyPI1Apache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: auditing an existing BOM, generating a new BOM, mapping to regulations, and listing required fields. There is no ambiguity in their roles.
Three tools follow a verb_noun pattern (audit_ai_bom_completeness, generate_ai_bom, map_to_regulation) but 'required_fields' is a noun phrase and not imperative, breaking the pattern. Also, 'map_to_regulation' includes a preposition while others do not.
4 tools is well-scoped for an AI BOM server, covering generation, auditing, regulatory mapping, and field reference. Not overloaded or insufficient.
Covers the core lifecycle: generate, audit, and map to regulations. A minor gap is the lack of a tool for updating or converting between BOM formats, but the format parameter in generate_ai_bom partially addresses this.