// MCP SERVER RECORD

Keycloak

Unverified
NPMkeycloak-mcp
DRisk gradehigh blast radius
Catalogue entry updated 8 days ago
Auth postureNot probedno remote endpoint probed yet
Tools91 Destructive · 3 Write · 5 Read
Worst categoryDestructivegrade tracks the peak, not the average
Capability mix
Destructive 1Write 3Read 5
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 9
delete-userDestructiveHighadd-user-to-groupWriteMediumassign-client-role-to-userWriteHighcreate-userWriteMediumlist-client-rolesReadLow
View all 9 tools
list-clientsReadLowlist-groupsReadLowlist-realmsReadLowlist-usersReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
delete-userdeny
add-user-to-grouprate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y keycloak-mcp

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.