loinc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOINC_PASSWORD | Yes | Your LOINC account password | |
| LOINC_USERNAME | Yes | Your LOINC account username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search LOINC codes by text. Returns matching codes with names and classifications. |
| get_codeA | Get full details for a LOINC code: name, parts, classification, units, and panel members/answer options if applicable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
get_code retrieves details for a specific code, while search finds codes by text. Their purposes are completely distinct, leaving no ambiguity.
Both names follow a simple verb pattern, but get_code uses verb_noun while search is just a verb. Slight inconsistency, though both are clear and predictable.
With only 2 tools, the server is minimal but covers basic search and retrieval for LOINC. It is slightly thin for a domain with many potential operations, yet acceptable for a focused utility.
The set covers core lookup and search but lacks operations like listing by class, navigating hierarchies, or batch queries. Notable gaps exist, but the two tools serve essential needs.