No user-submitted related servers found.
Scored across 18 tools
Most tools target clearly distinct resources or actions, and the detailed descriptions help distinguish static checks, live scans, code generation, and purpose management. However, guard_make_compliant overlaps with the specific generators (cookie banner, consent point, policy, compliance check), and guard_create_banner vs guard_generate_cookie_banner could be confused. These are manageable but not perfectly distinct.
All tools use the guard_ prefix and snake_case, with mostly predictable verb_noun patterns such as guard_get_scan_status, guard_create_purpose, and guard_update_purpose. Minor deviations like guard_login, guard_logout, and guard_explain are still readable and consistent with the overall convention.
18 tools serve two substantial clusters (compliance/scanning and purposes management) plus authentication, so the count is reasonable for the server's apparent scope. It is slightly on the heavy side, but each tool owns a distinct workflow step rather than being redundant.
Core LGPD workflows are well covered: local compliance checking, live site scanning, banner/consent/policy generation, finding explanations, login session handling, and purpose CRUD drafts. Minor gaps include no banner list/get/update/delete and no delete or archive operation for published purposes, though the agent-assisted surface can largely work around them.
