Skip to main content
Glama
mcp-polizei

mcp-polizei

by williamamed

Related Servers

Alternatives to mcp-polizei

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable clients to inspect and manage Keycloak realms, users, clients, roles, and groups with layered security modes, realm allowlisting, protected realms, delete gating, dry-run, and audit logging.
      8
      55 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables administration of Keycloak identity and access management through MCP, allowing management of realms, clients, users, roles, groups, identity providers, and sessions from any MCP client.
      Apache 2.0
    • F
      license
      A
      quality
      D
      maintenance
      Exposes user, membership, and role administration tools via MCP, acting as a thin passthrough to a coordinator API with RBAC enforced by the coordinator using caller bearer tokens.
      8
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Claude Code or Codex to administer a Bifrost LLM gateway's governance API, including virtual keys, teams, customers, budgets, provider configs, routing rules, model/pricing config, request-log observability, and core gateway config.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT

    TDQS

    C2.5/5.0

    Scored across 55 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as list_available_tenants vs list_tenants, list_oauth_scopes vs list_oauth_client_scopes, delete_scope vs delete_scope_own, and add_user_to_scope vs create_user. Even with descriptive notes, the high number of similarly named tools creates significant ambiguity.

    Naming Consistency2/5

    Naming mixes conventions: list_* vs get_*, create_* vs save_*, update_* vs set_* vs change_*, plus import, assign, remove, reject. Also, 'scope' and 'tenant' are used interchangeably, further breaking consistency.

    Tool Count1/5

    With 55 tools, the surface is overwhelming and far beyond typical scopes. The excessive count makes it impractical to browse and increases selection errors.

    Completeness2/5

    While covering many identity operations, there are notable gaps: no get_user (only list/search), no update_invitation, no direct user-permission assignment, and no get_role/get_permission by id. The large tool count does not correspond to complete lifecycle coverage.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data