Medical Terminologies MCP

Medical Terminologies MCP is, according to the provider, an independent remotely operated Model Context Protocol server from Sidney Bissoli. The official product page at https://medical.sidneybissoli.com/mcp names the Streamable HTTP endpoint, while the provider repository at https://github.com/SidneyBissoli/medical-terminologies-mcp describes the same service as an open-source project. Smithery lists sidneybissoli/medical-terminologies-mcp as verified and deployed and publishes the associated deployment endpoint. The product page, repository, Smithery metadata, and API information map that deployed endpoint to the same durable product identity. This catalog stores no credentials, tokens, API keys, secret values, or personal health data.

Purpose and documented scope

According to the provider, the server brings together tools for ICD-11, SNOMED CT, LOINC, RxNorm, MeSH, ATC, and Brazilian CID-10. The product page identifies WHO and NLM as important sources. The repository documents the World Health Organization for ICD-11, the National Library of Medicine and NIH for RxNorm and MeSH, LOINC as a terminology for laboratory and observation codes, the WHO Collaborating Centre context for ATC, and DataSUS V2008 for the bundled Brazilian CID-10. WHO describes ICD as an international classification and terminology for systematic recording and comparison of morbidity and mortality data. SNOMED CT is documented by the provider as optional and requiring an independently authorized Snowstorm instance; this entry does not promise a public, unrestricted SNOMED database.

According to the provider, tools can search codes, retrieve details and hierarchies, compare terminologies, and support mappings between sources. Responses include provenance such as source, canonical URL, data vintage, extraction time, and license where the relevant path provides it. That makes review easier, but it does not replace the primary source or a professional coding guideline. Terminology codes describe classifications, observations, or drug concepts; they are not a finding and not a diagnosis. This catalog entry and the server are informational only. They do not provide diagnosis, therapy, or treatment recommendations and must not be used to justify a clinical decision without qualified professional review.

Authorization, privacy, and data sharing

The provider describes the hosted endpoint without a visible access key in the product documentation. That does not guarantee that access, rate limits, availability, or terms will remain unchanged. Operators must review current provider and source documentation and allow only the expected host over TLS. If an upstream service such as the WHO ICD-11 API requires credentials, those credentials belong only in the relevant client's or service's protected configuration, never in prompts, logs, seeders, or the catalog.

Medical terminology queries can still create sensitive inferences when public codes are combined with search terms, case context, facilities, or timestamps. Before use, review data minimization, roles, retention, deletion, log access, storage region, subprocessors, and possible sharing with the connected model provider. A remote MCP server processes the request at its endpoint; a local MCP client does not automatically make responses local when it passes them to a hosted model, telemetry system, or log store.

Access restrictions, write access, and security

The documented terminology calls are primarily read-oriented. The service is not permission to modify WHO, NLM, LOINC, DataSUS, or other source datasets. Write access can nevertheless arise outside the server when a client transfers results into files, databases, reports, or clinical systems. Those actions require a separate role, least privilege, an approved destination, and human approval. SNOMED CT should be connected only through an appropriately authorized and secured local or organizational instance.

Tool responses, medical search text, and metadata are untrusted input and may contain prompt injection, incorrect mappings, or stale content. Use endpoint allowlisting, TLS, timeouts, bounded roles, minimal data sharing, source review, and auditable approvals. Check terminology version, language, scope, and license before reuse. The E-E-A-T basis of this entry is, according to the provider, the product page, the provider repository, Smithery deployment information, and the actually documented WHO, NLM, NIH, and DataSUS sources. These sources support identity and documented scope, not the correctness of every generated response.

An MCP client with Streamable HTTP support and network access to the official remote endpoint. WHO or optional SNOMED features may have separate permissions and source conditions that must be managed securely.

Add the official remote endpoint https://medical.sidneybissoli.com/mcp to the MCP client using current provider guidance. Before use, verify endpoint identity, tool schemas, roles, data sharing, source licenses, and access restrictions.

https://medical.sidneybissoli.com/mcp

The product page describes the remote endpoint without a visible key. Verify current authentication, rate limits, and upstream source requirements with the provider. Never store secrets in the catalog.

Terminology queries are read-oriented according to the documentation. Hosting and source APIs may impose roles, allowlisting, and access restrictions. External client writes require separate approval.

Queries reach the remote endpoint and responses may contain codes, metadata, and provenance. The connected client can share that data with logs, telemetry, or a model provider; minimize data and review retention.

Prompt injection, incorrect or stale mappings, sensitive inferences from search context, license violations, and unintended writes. Mitigate with TLS, allowlisting, least privilege, source review, and human approval.