mcpbeat

ACLM Lab Interpreter MCP Server

io.github.rabyavalla/aclm-lab-interpreter
answering

ACLM Lab Interpreter is answering right now. Last checked 4 min ago. It exposes 2 tools.

Interpret lab values against ACLM-optimized ranges. Returns deprescription signals.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
556 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add aclm-lab-interpreter --transport http https://web-production-ae61.up.railway.app/mcp/aclm-lab-interpreter
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "aclm-lab-interpreter": {
      "url": "https://web-production-ae61.up.railway.app/mcp/aclm-lab-interpreter"
    }
  }
}
~/.codex/config.toml
[mcp_servers.aclm-lab-interpreter]
url = "https://web-production-ae61.up.railway.app/mcp/aclm-lab-interpreter"
.cursor/mcp.json
{
  "mcpServers": {
    "aclm-lab-interpreter": {
      "url": "https://web-production-ae61.up.railway.app/mcp/aclm-lab-interpreter"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "aclm-lab-interpreter": {
      "url": "https://web-production-ae61.up.railway.app/mcp/aclm-lab-interpreter"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

interpret
interpret_labs
Interpret a panel of lab values against ACLM-optimized reference ranges. Returns risk classification per marker, lifestyle interventions, and medication deprescription signals.
marker
marker_reference
Look up the ACLM-optimized reference range and lifestyle intervention plan for a single biomarker (e.g., apob, lp_a, hscrp, hba1c, fasting_insulin, vitamin_d).

Endpoints

URLTransportStateLatencyChecked
https://web-production-ae61.up.railway.app/mcp/aclm-lab-interpreter streamable-http answering 398 ms 4 min ago

ACLM Lab Interpreter — questions

Answers built from our own checks of this server.

What can ACLM Lab Interpreter do?
It exposes 2 tools, read directly from the server on our last check. Among them: interpret_labs, marker_reference. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ACLM Lab Interpreter working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 556 ms. The bar chart above shows every period we have measured.
Is ACLM Lab Interpreter still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect ACLM Lab Interpreter?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ACLM Lab Interpreter need an API key?
No. ACLM Lab Interpreter completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ACLM Lab Interpreter?
It answers our handshake in 556 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.