Skip to content

Infermedica MCP by usefulapi

io.usefulapi/infermedicausefulapi.iostreamable-httpv1.40.4Scanned

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

17 tools: 5 change things and 12 only read.

Tools: 0 delete, 0 irreversible, 5 write, 12 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Infermedica MCP by usefulapi can do

The Infermedica MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 17 tools. It can create or change data (5 tools: infermedica_diagnosis, infermedica_triage, infermedica_suggest, infermedica_parse and 1 more), but cannot delete data. 12 tools only read.

1 tool reads private data (infermedica_search_concepts).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Changes things 5Claude Code: ask
  • infermedica_diagnosisRun the diagnostic engine over the collected evidence — returns the next question to ask, ranked candidate conditions with probabilities, and a should_stop flag.1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "infermedica_diagnosis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compute diagnosis
    • readOnlyHint: true
  • infermedica_parseExtract clinical mentions (symptoms / risk factors) and their states from free-text describing complaints, mapping them to Infermedica evidence ids (NLP).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Parse clinical text
    • readOnlyHint: true
  • infermedica_recommend_specialistRecommend the most appropriate medical specialist and consultation channel for the collected evidence (accepts the same body as diagnosis/triage).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Recommend specialist
    • readOnlyHint: true
  • infermedica_suggestSuggest additional symptoms/observations the patient is likely to have, to speed up the interview.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Suggest additional symptoms/observations the patient is likely to have, to speed up the interview. Non-mutating computation. Engine API: POST /suggest.

    Annotations the server declares

    • title: Suggest observations
    • readOnlyHint: true
  • infermedica_triageRecommend a triage level (emergency_ambulance | emergency | consultation_24 | consultation | self_care) plus any serious/emergency observations, given the evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compute triage
    • readOnlyHint: true
Only reads 12Show 12 read-only tools
  • infermedica_explainExplain which evidence supports or conflicts with a given target condition, for the collected evidence.No findings

    Why it is in this group

    • The name "infermedica_explain" says "explain": a word for reading.
    Description, as the server wrote it
    Explain which evidence supports or conflicts with a given target condition, for the collected evidence. Non-mutating computation. Engine API: POST /explain.

    Annotations the server declares

    • title: Explain condition
    • readOnlyHint: true
  • infermedica_get_conditionGet a single condition by its id.No findings

    Why it is in this group

    • The name "infermedica_get_condition" says "get": a word for reading.
    Description, as the server wrote it
    Get a single condition by its id. Engine API: GET /conditions/{id}.

    Annotations the server declares

    • title: Get condition
    • readOnlyHint: true
  • infermedica_get_infoGet metadata about the current Infermedica medical model (version, last update, concept counts).No findings

    Why it is in this group

    • The name "infermedica_get_info" says "get": a word for reading.
    Description, as the server wrote it
    Get metadata about the current Infermedica medical model (version, last update, concept counts). Engine API: GET /info.

    Annotations the server declares

    • title: Get model info
    • readOnlyHint: true
  • infermedica_get_lab_testGet a single lab test by its id.No findings

    Why it is in this group

    • The name "infermedica_get_lab_test" says "get": a word for reading.
    Description, as the server wrote it
    Get a single lab test by its id. Engine API: GET /lab_tests/{id}.

    Annotations the server declares

    • title: Get lab test
    • readOnlyHint: true
  • infermedica_get_risk_factorGet a single risk factor by its id.No findings

    Why it is in this group

    • The name "infermedica_get_risk_factor" says "get": a word for reading.
    Description, as the server wrote it
    Get a single risk factor by its id. Engine API: GET /risk_factors/{id}.

    Annotations the server declares

    • title: Get risk factor
    • readOnlyHint: true
  • infermedica_get_symptomGet a single symptom by its id.No findings

    Why it is in this group

    • The name "infermedica_get_symptom" says "get": a word for reading.
    Description, as the server wrote it
    Get a single symptom by its id. Engine API: GET /symptoms/{id}.

    Annotations the server declares

    • title: Get symptom
    • readOnlyHint: true
  • infermedica_list_conditionsList all conditions (diseases) in the Infermedica medical model.No findings

    Why it is in this group

    • The name "infermedica_list_conditions" says "list": a word for reading.
    Description, as the server wrote it
    List all conditions (diseases) in the Infermedica medical model. Engine API: GET /conditions.

    Annotations the server declares

    • title: List conditions
    • readOnlyHint: true
  • infermedica_list_lab_testsList all lab tests (and their results) in the Infermedica medical model.No findings

    Why it is in this group

    • The name "infermedica_list_lab_tests" says "list": a word for reading.
    Description, as the server wrote it
    List all lab tests (and their results) in the Infermedica medical model. Engine API: GET /lab_tests.

    Annotations the server declares

    • title: List lab tests
    • readOnlyHint: true
  • infermedica_list_risk_factorsList all risk factors in the Infermedica medical model.No findings

    Why it is in this group

    • The name "infermedica_list_risk_factors" says "list": a word for reading.
    Description, as the server wrote it
    List all risk factors in the Infermedica medical model. Engine API: GET /risk_factors.

    Annotations the server declares

    • title: List risk factors
    • readOnlyHint: true
  • infermedica_list_symptomsList all symptoms in the Infermedica medical model (optionally age-filtered).No findings

    Why it is in this group

    • The name "infermedica_list_symptoms" says "list": a word for reading.
    Description, as the server wrote it
    List all symptoms in the Infermedica medical model (optionally age-filtered). Engine API: GET /symptoms.

    Annotations the server declares

    • title: List symptoms
    • readOnlyHint: true
  • infermedica_rationaleExplain WHY the diagnostic engine wants to ask its next question, given the evidence.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    Explain WHY the diagnostic engine wants to ask its next question, given the evidence. Non-mutating computation. Engine API: POST /rationale.

    Annotations the server declares

    • title: Get question rationale
    • readOnlyHint: true
  • infermedica_search_conceptsSearch the medical concept database for observations matching a phrase (autocomplete).Reads private dataNo findings

    Why it is in this group

    • The name "infermedica_search_concepts" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "database": it reads databases.
    Description, as the server wrote it
    Search the medical concept database for observations matching a phrase (autocomplete). Engine API: GET /search.

    Annotations the server declares

    • title: Search concepts
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://infermedica.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://infermedica.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "infermedica_diagnosis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://infermedica.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://infermedica.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http infermedica https://infermedica.usefulapi.io/mcp
claude mcp add --transport http infermedica https://infermedica.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__infermedica__infermedica_list_symptoms",
      "mcp__infermedica__infermedica_get_symptom",
      "mcp__infermedica__infermedica_list_conditions",
      "mcp__infermedica__infermedica_get_condition",
      "mcp__infermedica__infermedica_list_risk_factors",
      "mcp__infermedica__infermedica_get_risk_factor",
      "mcp__infermedica__infermedica_list_lab_tests",
      "mcp__infermedica__infermedica_get_lab_test",
      "mcp__infermedica__infermedica_search_concepts",
      "mcp__infermedica__infermedica_get_info",
      "mcp__infermedica__infermedica_explain",
      "mcp__infermedica__infermedica_rationale"
    ],
    "ask": [
      "mcp__infermedica__infermedica_diagnosis",
      "mcp__infermedica__infermedica_triage",
      "mcp__infermedica__infermedica_suggest",
      "mcp__infermedica__infermedica_parse",
      "mcp__infermedica__infermedica_recommend_specialist"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as infermedica. Review it before you use it.

Capability tags behind 1 rule
  • mcp__infermedica__infermedica_search_concepts private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/infermedica/verify?hash=078d996a0a21870055a6503fdc8d7b38e22bb6bd4bcaae778ea5ab371cff0e81" | jq -e '.changed == false'

Pinned hash 078d996a0a21, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/infermedica/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/infermedica
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/infermedica.svg)](https://radar.anlyon.com/servers/io.usefulapi/infermedica)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Infermedica MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Infermedica MCP by usefulapi safe?

No scan can promise that. What its definitions show: 17 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Infermedica MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Infermedica MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Infermedica MCP by usefulapi have?

17 tools: 5 write, 12 read. infermedica_diagnosis, infermedica_triage, infermedica_suggest, infermedica_parse, infermedica_recommend_specialist, infermedica_list_symptoms, infermedica_get_symptom, infermedica_list_conditions and 9 more.

Does the Infermedica MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Infermedica MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Infermedica MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.