Is the Aks129 Healthclaw Guardrails MCP server down?

mcp-registry/io.github.aks129/healthclaw-guardrails · v1.0.0

Also listed as glama/aks129/healthclawguardrails

As of 2026-10-24 11:32 UTC, the Aks129 Healthclaw Guardrails MCP server is up (it requires sign-in) with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation

claude mcp add --transport http aks129-healthclaw-guardrails-mcp-server https://mcp-server-production-5112.up.railway.app/mcp

{
  "mcpServers": {
    "aks129-healthclaw-guardrails-mcp-server": {
      "type": "http",
      "url": "https://mcp-server-production-5112.up.railway.app/mcp"
    }
  }
}

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

Agent-readiness: A (92/100)

What to fix (3)

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.aks129/healthclaw-guardrails"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.aks129/healthclaw-guardrails"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,731 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• fhir_search ~432 tokens
• shl_generate ~309 tokens
• curatr_apply_fix ~288 tokens
• rx_transfer_request ~287 tokens
• fhir_read ~267 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aks129%2Fhealthclaw-guardrails.svg)](https://glimind.com/server/mcp-registry%2Fio.github.aks129%2Fhealthclaw-guardrails?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.aks129%2Fhealthclaw-guardrails?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aks129%2Fhealthclaw-guardrails.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aks129%2Fhealthclaw-guardrails.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.aks129%2Fhealthclaw-guardrails?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:0e53752e2f7858a2…, first seen 2026-10-17, included at leaf 15132 of 58,738. Version history · verify what your client received.

Tools (29)

• action_commit
• action_propose
• action_status
• care_gaps
• context_get
• curatr_apply_fix
• curatr_evaluate
• fetch
• fhir_commit_write
• fhir_compiled_truth
• fhir_get_token
• fhir_interpret_labs
• fhir_lastn
• fhir_permission_evaluate
• fhir_propose_write
• fhir_read
• fhir_search
• fhir_seed
• fhir_stats
• fhir_subscription_topics
• fhir_validate
• guardrail_conformance
• questionnaire_extract
• questionnaire_populate
• rx_transfer_request
• search
• shl_generate
• sources_check
• wearables_sync_status

Compare: most reliable communication servers · most reliable other servers · most reliable healthcare servers · most reliable data servers · most reliable retrieval servers

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

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

FAQ

Is the Aks129 Healthclaw Guardrails MCP server down right now?

As of 2026-10-24 11:32 UTC, the Aks129 Healthclaw Guardrails MCP server is up (it requires sign-in) with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Aks129 Healthclaw Guardrails MCP server provide?

Aks129 Healthclaw Guardrails MCP server advertises 29 tools, including action_commit, action_propose, action_status, care_gaps, context_get.

How do I install Aks129 Healthclaw Guardrails MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp-server-production-5112.up.railway.app/mcp

Is the Aks129 Healthclaw Guardrails MCP server safe to connect to an AI agent?

Glimind scanned all 29 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 Aks129 Healthclaw Guardrails 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.