policy-drift
Related Servers
Alternatives to policy-drift
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGenerates legal policies (privacy, terms, cookies, etc.) directly from AI coding tools by analyzing codebase context.16MIT
- AlicenseCqualityBmaintenanceEnables local-first, fail-closed security auditing of AI coding outputs by detecting Korean PII, secrets, configuration risks, and MCP-native threats, while mediating runtime events and gating releases with actionable verdicts and next steps.28MIT
- AlicenseAqualityBmaintenanceOne-step legal compliance for vibe-coded apps: scans project, generates privacy policies/TOS, installs cookie consent banner, and checks EU AI Act risk.10175 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and retrieve Korean laws, regulations, administrative rules, legal interpretations, and precedents via official APIs for legal review workflows.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to generate privacy policies, terms of service, EULAs, cookie policies, and disclaimers directly within the development workflow, with free previews and optional full-document unlocking via a one-time license key.645 npmMIT
- AlicenseAqualityBmaintenanceEnables natural language interaction with the Korean Personal Information Protection Act (PIPA) through 37 MCP tools that search, compare, analyze, and verify legal texts, official guidelines, and consulting cases from authoritative sources.3738 npm4MIT
TDQS
Scored across 5 tools
Each tool targets a distinct phase of the policy-drift workflow: inventory, change diff, policy reading, checklist lookup, and full audit. The boundaries between scan_data_map, scan_changes, and audit are mostly clear, though an agent may occasionally hesitate between scan_changes and audit without reading descriptions carefully.
Most names follow a readable verb_noun or clear action pattern: scan_data_map, scan_changes, get_policies, get_checklist. The lone 'audit' is a verb/noun hybrid but remains understandable and does not disrupt the overall pattern.
Five tools is well-scoped for a policy-drift analysis server, covering the core workflow without redundant operations. Each tool has a clear role in the inventory, diff, read, checklist, and audit sequence.
The surface covers the main analysis lifecycle: code scanning, change detection, policy reading, jurisdiction checklist, and full audit. Minor gaps exist around updating policies or inspecting configuration, but these may be intentionally out of scope for a read-only drift-analysis server.