Keycloak (PyPI) MCP Server

mcp-keycloak PyPI v1.2.2

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for Keycloak administration

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 78

Each tool and what it can reach — statically extracted from the published source.

  • add_execution_to_flowno sensitive capability
  • add_realm_default_groupno sensitive capability
  • add_subflow_to_flowno sensitive capability
  • add_user_to_groupno sensitive capability
  • assign_client_role_to_userno sensitive capability
  • assign_realm_role_to_userno sensitive capability
  • copy_authentication_flowno sensitive capability
  • count_usersno sensitive capability
  • create_authentication_flowno sensitive capability
  • create_authenticator_configno sensitive capability
Show 68 more tools ↓
  • create_clientno sensitive capability
  • create_client_roleno sensitive capability
  • create_executionno sensitive capability
  • create_groupno sensitive capability
  • create_realm_roleno sensitive capability
  • create_userno sensitive capability
  • delete_authentication_flowno sensitive capability
  • delete_authenticator_configno sensitive capability
  • delete_clientno sensitive capability
  • delete_executionno sensitive capability
  • delete_groupno sensitive capability
  • delete_realm_roleno sensitive capability
  • delete_userno sensitive capability
  • get_accessible_realmsno sensitive capability
  • get_authentication_flowno sensitive capability
  • get_authenticator_configno sensitive capability
  • get_authenticator_providersno sensitive capability
  • get_clientno sensitive capability
  • get_client_authenticator_providersno sensitive capability
  • get_client_by_clientidno sensitive capability
  • get_client_secretno sensitive capability
  • get_client_service_accountno sensitive capability
  • get_executionno sensitive capability
  • get_execution_configno sensitive capability
  • get_flow_executionsno sensitive capability
  • get_groupno sensitive capability
  • get_group_membersno sensitive capability
  • get_provider_config_descriptionno sensitive capability
  • get_realm_default_groupsno sensitive capability
  • get_realm_events_configno sensitive capability
  • get_realm_infono sensitive capability
  • get_realm_roleno sensitive capability
  • get_required_actionno sensitive capability
  • get_required_actionsno sensitive capability
  • get_unregistered_required_actionsno sensitive capability
  • get_userno sensitive capability
  • get_user_groupsno sensitive capability
  • get_user_realm_rolesno sensitive capability
  • get_user_sessionsno sensitive capability
  • list_authentication_flowsno sensitive capability
  • list_client_rolesno sensitive capability
  • list_clientsno sensitive capability
  • list_groupsno sensitive capability
  • list_realm_rolesno sensitive capability
  • list_usersno sensitive capability
  • logout_userno sensitive capability
  • lower_execution_priorityno sensitive capability
  • lower_required_action_priorityno sensitive capability
  • raise_execution_priorityno sensitive capability
  • raise_required_action_priorityno sensitive capability
  • regenerate_client_secretno sensitive capability
  • register_required_actionno sensitive capability
  • remove_all_user_sessionsno sensitive capability
  • remove_realm_default_groupno sensitive capability
  • remove_realm_role_from_userno sensitive capability
  • remove_user_from_groupno sensitive capability
  • reset_user_passwordno sensitive capability
  • update_authentication_flowno sensitive capability
  • update_authenticator_configno sensitive capability
  • update_clientno sensitive capability
  • update_execution_configno sensitive capability
  • update_flow_executionsno sensitive capability
  • update_groupno sensitive capability
  • update_realm_events_configno sensitive capability
  • update_realm_roleno sensitive capability
  • update_realm_settingsno sensitive capability
  • update_required_actionno sensitive capability
  • update_userno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.2 latest A 98/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-keycloak/badge.svg)](https://mcptrustchecker.com/registry/mcp-keycloak)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-keycloak"><img src="https://mcptrustchecker.com/registry/mcp-keycloak/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-keycloak/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-keycloak --online --registry pypi

Use the free API → How scoring works

Other implementations of Keycloak 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Security & Testing