No user-submitted related servers found.
Scored across 29 tools
Most tools are clearly separated by resource (client, user, group, session, events) and action (list, detail, audit, revoke, rotate). The main ambiguity is between client_session_stats and client_sessions (both are per-client session reads, one aggregate and one detailed), and between login_failure_rca and login_events (both read auth events, one is an RCA analysis, one is a raw feed). Descriptions are detailed enough to resolve these, but an agent could still pause on those pairs.
The set mostly follows a verb_noun pattern: list_clients, list_users, list_groups, user_detail, user_sessions, disable_user, enable_user, revoke_user_sessions, require_password_reset, update_client_redirect_uris, rotate_client_secret. Deviations include identity_overview, realm_info, undo_list, undo_apply, and the *_audit / *_analysis / *_rca tools, which use noun_verb or noun-only names. Still, the pattern is readable and predictable enough.
29 tools is on the heavy side for an identity/IdP server, but the domain is broad (users, clients, groups, sessions, events, audits, MFA, undo). Each tool has a distinct purpose and the count is justified by the scope, though it is approaching the upper bound where navigation becomes costly.
The server covers the identity lifecycle well: read users/clients/groups, user state changes (disable/enable/reset/revoke), client remediation (redirect URIs, secret rotation), audits, and an undo mechanism. Gaps include no direct user creation/deletion, no group membership modification, and no client creation/deletion, but the stated purpose is identity AIOps (monitoring and remediation) rather than full IdP administration, so the surface is largely complete for that purpose.