Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/infermedica

REMOTE · INFERMEDICA.USEFULAPI.IO · SCANNED OCT 4

Run Infermedica symptom checks, diagnosis, triage and condition lookups.

76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2471 tokens (~145/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.usefulapi/infermedica MCP server?

io.usefulapi/infermedica is a hosted endpoint at https://infermedica.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · infermedica.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-infermedica 'https://infermedica.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-infermedica": {
      "url": "https://infermedica.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-infermedica": {
      "type": "http",
      "url": "https://infermedica.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-infermedica]
url = "https://infermedica.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-infermedica": {
      "type": "remote",
      "url": "https://infermedica.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-infermedica --url 'https://infermedica.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-infermedica:
    url: "https://infermedica.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-infermedica": {
      "Transport": "http",
      "Url": "https://infermedica.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-infermedica -t streamable-http -u 'https://infermedica.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-infermedica": {
      "type": "http",
      "url": "https://infermedica.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 0
    • Server version: 1.3.0 → 1.5.1 functional
  • 1 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.3.0 functional
  • 30 Sept 26 +42
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • First check of Authorization: partial security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 95 functional
    • First check of Schema quality: good functional
  • 29 Sept 26 28

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Oct 2026 · Probed https://infermedica.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of infermedica.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://infermedica.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://infermedica.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://infermedica.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://infermedica.usefulapi.io/mcp
Authorisation server https://infermedica.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://infermedica.usefulapi.io/mcp Verified 200
http (plaintext) http://infermedica.usefulapi.io/mcp HTTPS enforced 301 https://infermedica.usefulapi.io/mcp
MCP tools · 17 exposed · ~2,471 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
infermedica_diagnosis ~187

Run the diagnostic engine over the collected evidence — returns the next question to ask, ranked candidate conditions with probabilities, and a should_stop flag. Non-mutating computation. Engine API: POST /diagnosis.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
evidencearray–Evidence collected so far (may be empty for the first call).
extrasobject–Optional engine flags (e.g. disable_groups, enable_triage_5).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.

No output schema declared.

No examples provided.

infermedica_explain ~188

Explain which evidence supports or conflicts with a given target condition, for the collected evidence. Non-mutating computation. Engine API: POST /explain.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
evidencearray–List of observed evidence (symptoms / risk factors / lab tests) and their states.
extrasobject––
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.
targetstringyesTarget condition id to explain, e.g. 'c_49' (required).

No output schema declared.

No examples provided.

infermedica_get_condition ~109

Get a single condition by its id. Engine API: GET /conditions/{id}.

NameTypeReqDescription
ageobject–Optional age context.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
idstringyesCondition id, e.g. 'c_87' (required).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_get_info ~98

Get metadata about the current Infermedica medical model (version, last update, concept counts). Engine API: GET /info.

NameTypeReqDescription
ageobject–Optional age context.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_get_lab_test ~113

Get a single lab test by its id. Engine API: GET /lab_tests/{id}.

NameTypeReqDescription
ageobject–Optional age context.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
idstringyesLab test id, e.g. 'lt_1' (required).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_get_risk_factor ~115

Get a single risk factor by its id. Engine API: GET /risk_factors/{id}.

NameTypeReqDescription
ageobject–Optional age context.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
idstringyesRisk factor id, e.g. 'p_28' (required).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_get_symptom ~112

Get a single symptom by its id. Engine API: GET /symptoms/{id}.

NameTypeReqDescription
ageobject–Optional age context.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
idstringyesSymptom id, e.g. 's_21' (required).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_list_conditions ~95

List all conditions (diseases) in the Infermedica medical model. Engine API: GET /conditions.

NameTypeReqDescription
ageobject–Optional age filter.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_list_lab_tests ~98

List all lab tests (and their results) in the Infermedica medical model. Engine API: GET /lab_tests.

NameTypeReqDescription
ageobject–Optional age filter.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_list_risk_factors ~96

List all risk factors in the Infermedica medical model. Engine API: GET /risk_factors.

NameTypeReqDescription
ageobject–Optional age filter.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_list_symptoms ~131

List all symptoms in the Infermedica medical model (optionally age-filtered). Engine API: GET /symptoms.

NameTypeReqDescription
ageobject–Optional age filter (returns only age-relevant symptoms).
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
enable_triage_5boolean–If true, include symptoms only used by the 5-level triage model.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.

No output schema declared.

No examples provided.

infermedica_parse ~234

Extract clinical mentions (symptoms / risk factors) and their states from free-text describing complaints, mapping them to Infermedica evidence ids (NLP). Non-mutating computation. Engine API: POST /parse.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
concept_typesarray–Restrict captured mentions to these concept types.
contextarray–Ordered ids of already-captured present symptoms, used as parsing context.
correct_spellingboolean–If true, correct spelling of the input before analysis.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
include_tokensboolean–If true, include tokenization details in the output.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.
textstringyesFree-text describing the patient's complaints (required).

No output schema declared.

No examples provided.

infermedica_rationale ~164

Explain WHY the diagnostic engine wants to ask its next question, given the evidence. Non-mutating computation. Engine API: POST /rationale.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
evidencearray–List of observed evidence (symptoms / risk factors / lab tests) and their states.
extrasobject––
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.

No output schema declared.

No examples provided.

infermedica_recommend_specialist ~187

Recommend the most appropriate medical specialist and consultation channel for the collected evidence (accepts the same body as diagnosis/triage). Non-mutating computation. Engine API: POST /recommend_specialist.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
evidencearray–List of observed evidence (symptoms / risk factors / lab tests) and their states.
extrasobject–Optional flags (e.g. a specialist_mapping remap).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.

No output schema declared.

No examples provided.

infermedica_search_concepts ~154

Search the medical concept database for observations matching a phrase (autocomplete). Engine API: GET /search.

NameTypeReqDescription
ageobject–Optional age filter.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
max_resultsinteger–Maximum number of results to return (default 8).
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
phrasestringyesText phrase to match against concept names/synonyms (required).
sexstring–Optional sex filter.
typesarray–Restrict results to these concept types.

No output schema declared.

No examples provided.

infermedica_suggest ~207

Suggest additional symptoms/observations the patient is likely to have, to speed up the interview. Non-mutating computation. Engine API: POST /suggest.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
evidencearray–List of observed evidence (symptoms / risk factors / lab tests) and their states.
extrasobject––
max_resultsinteger–Maximum number of suggestions.
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.
suggest_methodstring–Which kind of observations to suggest (default 'symptoms'). Sent as the `suggest_method` query param.

No output schema declared.

No examples provided.

infermedica_triage ~183

Recommend a triage level (emergency_ambulance | emergency | consultation_24 | consultation | self_care) plus any serious/emergency observations, given the evidence. Non-mutating computation. Engine API: POST /triage.

NameTypeReqDescription
ageobjectyesPatient age, e.g. { value: 30 } or { value: 6, unit: 'month' }.
dev_modeboolean–If true, mark the request as test traffic → sends the `Dev-Mode: true` header.
evidencearray–List of observed evidence (symptoms / risk factors / lab tests) and their states.
extrasobject––
model_idstring–Optional medical model id → sent as the `Model-Id` request header.
sexstringyesPatient biological sex.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/infermedica MCP server?

io.usefulapi/infermedica is an MCP server listed in the public MCP registry as io.usefulapi/infermedica. Run Infermedica symptom checks, diagnosis, triage and condition lookups. This page covers its hosted endpoint (https://infermedica.usefulapi.io/mcp).

Is the io.usefulapi/infermedica MCP server safe to use?

io.usefulapi/infermedica scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.usefulapi/infermedica MCP server expose?

io.usefulapi/infermedica exposes 17 tools: infermedica_list_symptoms, infermedica_get_symptom, infermedica_list_conditions, infermedica_get_condition, infermedica_list_risk_factors, and 12 more. Their descriptions and schemas cost roughly 2,471 tokens of context every time the server is loaded.

Does the io.usefulapi/infermedica MCP server require authentication?

Yes. io.usefulapi/infermedica asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.usefulapi/infermedica MCP server still maintained?

io.usefulapi/infermedica is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.