mcp-semclone
Related Servers
Alternatives to mcp-semclone
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI coding agents to audit Python and npm dependency licenses against your distribution context before shipping, returning CLEAN, REVIEW, or BLOCK verdicts with plain-language reasons and supporting notice generation.31MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to perform vulnerability scanning on Docker/OCI images, check CVE details, analyze licenses, and compare scan results via ScanRook.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables automated security code auditing using LLM and MCP, including AST parsing, taint analysis, dataflow tracing, and automated PoC generation for multi-language codebases.1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to run deterministic, fully local static security and compliance audits of code, configurations, and dependencies through 32 MCP tools covering 24 vulnerability categories. It also detects the project stack, generates risk reports and checklists, suggests stack-aware remediations, and re-validates fixes to confirm vulnerabilities were eliminated.321MIT
- AlicenseAqualityBmaintenanceEnables AI agents to inventory dependency licenses from lockfiles mostly offline, normalize them to SPDX, check them against policy, assess compatibility, and draft third-party notices.6MIT
- AlicenseAqualityBmaintenanceSecurity checks for code an AI agent is about to trust. vetcode_guard checks a command before it installs packages or adds an MCP server: made-up names, look-alikes, malware advisories, brand-new releases, and the archive read without running it. vetcode_scan reads a folder for malware, supply-chain attacks, attacks on agents, leaked secrets and risky config. Local, zero dependencies.42MIT
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose. While generate_legal_notices and generate_legal_notices_from_purls are similar, their descriptions explicitly differentiate them by input method and use case, preventing confusion. All other tools target unique aspects of compliance analysis.
Tool names predominantly follow a verb_noun pattern (e.g., scan_directory, validate_policy), but there is minor inconsistency: some use hyphens (check_license_compatibility) while others use underscores consistently, and verbs vary (analyze, check, generate, scan, validate). Overall, the pattern is predictable and readable.
With 14 tools, the server covers a comprehensive compliance workflow—from scanning and package analysis to license validation, legal notice generation, and SBOM creation. Each tool serves a clear role without redundancy, and the count is well-scoped for the domain.
The tool surface covers the entire lifecycle: scanning (source, binary), package analysis (simple and deep), license checks (details, obligations, compatibility), risk assessment, policy validation, legal notices (source and PURL-based), SBOM generation, and an end-to-end compliance workflow. No significant gaps are apparent.