Is the Heintonny Keycloak Mcp.test MCP server down?

mcp-registry/io.github.heintonny/keycloak-mcp.test · v1.26.0

healthy
Last checked 2026-10-19 14:44 UTC · handshake 566ms

As of 2026-10-19 14:44 UTC, the Heintonny Keycloak Mcp.test MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.9%
checks observed
3,872
outages (90d)
7
tools
6

This is just a test publish, delete me

Install Heintonny Keycloak Mcp.test MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http heintonny-keycloak-mcp-test-mcp-server https://keycloak-mcp.test.happi.hafslund.no/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "heintonny-keycloak-mcp-test-mcp-server": {
      "type": "http",
      "url": "https://keycloak-mcp.test.happi.hafslund.no/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 4 warning(s) across 6 tool(s); ~826 tokens of tool definitions.
Scores higher than 6% of 15,354 MCP servers Glimind has audited.
Its tool list costs an agent ~826 tokens per session — lighter than 80% of servers.
71 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints7
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (4)

9 parameter(s) across 6 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: analyze_keycloak_deployment, explain_keycloak_component, explain_keycloak_protocol, keycloak_config_reference, keycloak_explain and 1 more

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: analyze_keycloak_deployment, explain_keycloak_component, explain_keycloak_protocol, keycloak_config_reference, keycloak_explain and 1 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: analyze_keycloak_deployment

Handshake + tools/list takes ~2,199 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test/fixes

analyze_keycloak_deployment 1 change
{
  "name": "analyze_keycloak_deployment",
  "description": "\n    Analyze Keycloak deployment configuration and identify potential issues or provide recommendations.\n    \n    Input deployment_info should include:\n      - keycloak_version: version string\n      - deployment_type: (standalone, clustered)\n      - database: database type (postgresql, mysql, h2)\n      - protocol: (http, https)\n      - cache_type: (local, infinispan)\n      - auth_providers: list of configured identity providers\n      - any warnings or alerts\n    \n    Returns structured analysis ",
  "inputSchema": {
    "type": "object",
    "title": "analyze_keycloak_deploymentArguments",
    "required": [
      "deployment_info"
    ],
    "properties": {
      "deployment_info": {
        "type": "object",
        "title": "Deployment Info",
        "additionalProperties": true
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
explain_keycloak_component 1 change
{
  "name": "explain_keycloak_component",
  "description": "\n    Explain a Keycloak component (realm, client, user, role, provider, mapper).\n    Returns description and relevant documentation snippets.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "explain_keycloak_componentArguments",
    "required": [
      "component_type"
    ],
    "properties": {
      "component_type": {
        "type": "string",
        "title": "Component Type"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
explain_keycloak_protocol 1 change
{
  "name": "explain_keycloak_protocol",
  "description": "\n    Explain Keycloak protocols (oidc, saml, oauth2).\n    Returns description and relevant documentation snippets.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "explain_keycloak_protocolArguments",
    "required": [
      "protocol_type"
    ],
    "properties": {
      "protocol_type": {
        "type": "string",
        "title": "Protocol Type"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.heintonny/keycloak-mcp.test"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.heintonny/keycloak-mcp.test"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test.svg)](https://glimind.com/server/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.heintonny%2Fkeycloak-mcp.test?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:15f8531eb3bb3bb8…, first seen 2026-10-17, included at leaf 9911 of 27,239. Version history · verify what your client received.

Tools (6)

Compare: most reliable devops servers · most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Heintonny Keycloak Mcp.test MCP server down right now?

As of 2026-10-19 14:44 UTC, the Heintonny Keycloak Mcp.test MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Heintonny Keycloak Mcp.test MCP server provide?

Heintonny Keycloak Mcp.test MCP server advertises 6 tools, including analyze_keycloak_deployment, explain_keycloak_component, explain_keycloak_protocol, keycloak_config_reference, keycloak_explain.

How do I install Heintonny Keycloak Mcp.test MCP server?

Point your MCP client at this streamable-http endpoint: https://keycloak-mcp.test.happi.hafslund.no/mcp

Is the Heintonny Keycloak Mcp.test MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Heintonny Keycloak Mcp.test MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve