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.github.SLAtech-IL/mediora-mcp

REMOTE · MCP.MEDIORA.AI · SCANNED SEP 24

Doctor-reviewed blood-test markers, conditions & symptoms as agent tools. EN/RU/HE. Hosted.

Available components

0 this week 77 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 Security57
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1678 tokens (~119/item across 14 items; 14 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.SLAtech-IL/mediora-mcp server?

io.github.SLAtech-IL/mediora-mcp is a hosted endpoint at https://mcp.mediora.ai/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 · mcp.mediora.ai

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

  • 1 Sept 26 0
    • Tool “mediora__explain_marker” rewrote its description, which is the text the model reads security
  • 26 Aug 26 77
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    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 24 Sept 2026 · Probed https://mcp.mediora.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mediora.ai CN=WE1,O=Google Trust Services,C=US 5 Sept 2026 4 Dec 2026 ECDSA 256 ECDSA-SHA256 bd5fb2927c937ab00eb9060049c44039
SANs: mediora.ai, *.mediora.ai
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 mcp.mediora.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
mediora.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.mediora.ai/mcp Verified 200
http (plaintext) http://mcp.mediora.ai/mcp HTTPS enforced 301 https://mcp.mediora.ai/mcp
MCP tools · 14 exposed · ~1,678 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
mediora__analyze_lab_pdf ~154

Upload a lab-report PDF or scan (by HTTPS URL) and trigger Mediora.AI's full Vision + analysis pipeline. Returns a pending test id the client can poll. The URL must be https, must resolve to a public IP (no localhost / cloud-metadata / private LAN), and the file must be PDF / JPEG / PNG ≤ 10 MB. Redirects are not followed — pass the final URL.

NameTypeReqDescription
bearer_tokenstringyesMediora.AI patient JWT (see mediora__whoami).
file_urlstringyesPublic HTTPS URL of the lab-report PDF to analyze.
languagestring–Preferred language for the analysis output. Defaults to 'en'.

No output schema declared.

No examples provided.

mediora__explain_condition ~107

Return the full explainer for a clinical condition by slug. Includes: what the condition is, the key markers used in diagnosis, common symptoms, and when the patient should seek clinical evaluation.

NameTypeReqDescription
langstring–Language code. Defaults to 'en'.
slugstringyesMediora canonical slug (e.g. 'hba1c', 'ferritin'). Use mediora__list_markers / mediora__list_conditions to discover slugs.

No output schema declared.

No examples provided.

mediora__explain_marker ~152

Return the full explainer for a single blood-test marker by slug. Includes: what it measures, what high/low values mean, when the value is clinically actionable, the conditions typically associated with it, and - where habits genuinely move the number - what can be done about a high or low result. Those action fields are empty when the value follows an underlying cause rather than lifestyle, which is itself the answer.

NameTypeReqDescription
langstring–Language code. Defaults to 'en'.
slugstringyesMediora canonical slug (e.g. 'hba1c', 'ferritin'). Use mediora__list_markers / mediora__list_conditions to discover slugs.

No output schema declared.

No examples provided.

mediora__explain_panel ~152

Return the markers that make up a lab panel by slug — each resolved to its Mediora marker slug, name and one-line summary — plus the panel's search aliases (CBC/FBC, CMP, LFT, TFT, renal panel, …). Answers "what's included in a CBC / lipid panel / CMP". Follow each marker into mediora__explain_marker for full detail.

NameTypeReqDescription
langstring–Language for the marker names/summaries. Defaults to 'en'.
slugstringyesPanel slug (e.g. 'complete-blood-count', 'lipid-panel', 'comprehensive-metabolic-panel'). Use mediora__list_panels to discover slugs.

No output schema declared.

No examples provided.

mediora__explain_symptom ~138

Return the full triage explainer for a single symptom by slug. Includes: what the symptom means, common causes, the lab work-up a clinician would order, and when the patient should seek urgent evaluation. The related marker and condition slug arrays let the upstream LLM follow the graph into mediora__explain_marker / explain_condition.

NameTypeReqDescription
langstring–Language code. Defaults to 'en'.
slugstringyesMediora canonical slug (e.g. 'hba1c', 'ferritin'). Use mediora__list_markers / mediora__list_conditions to discover slugs.

No output schema declared.

No examples provided.

mediora__get_patient_history ~142

Return the patient's past medical-test rows (id, test type, test date, risk level, summary, status, abnormal-marker count). Bearer token must be a Mediora patient-scope JWT. Paginated; default 10 per page. Proxies https://api.mediora.ai/api/medical-tests with the user's token forwarded as Authorization: Bearer.

NameTypeReqDescription
bearer_tokenstringyesMediora.AI patient JWT (see mediora__whoami).
pageinteger–1-based page number. Defaults to 1.
page_sizeinteger–Items per page. Defaults to 10, max 50.

No output schema declared.

No examples provided.

mediora__get_test_details ~144

Return the persisted markers + AI analysis (Summary, KeyFindings, Recommendations, DetailedExplanation) for a specific medical-test the authenticated patient owns. Use after mediora__get_patient_history surfaces a test id the user wants to discuss. Bearer token must be a Mediora patient-scope JWT. Proxies https://api.mediora.ai/api/medical-tests/{id} with the user's token forwarded as Authorization: Bearer.

NameTypeReqDescription
bearer_tokenstringyesMediora.AI patient JWT (see mediora__whoami).
test_idintegeryesNumeric medical-test id (returned by mediora__get_patient_history as `id`).

No output schema declared.

No examples provided.

mediora__list_conditions ~60

List every clinical condition in the Mediora catalog. Returns slug + name + ICD-10 code per entry. Use mediora__explain_condition for the full explainer.

NameTypeReqDescription
langstring–Language code. Defaults to 'en'.

No output schema declared.

No examples provided.

mediora__list_markers ~58

List every blood-test marker in the Mediora catalog. Returns slug + short name per entry. Use mediora__explain_marker for the full explainer.

NameTypeReqDescription
langstring–Language code. Defaults to 'en'.

No output schema declared.

No examples provided.

mediora__list_panels ~79

List every lab panel in the Mediora catalog (CBC, lipid, comprehensive metabolic, thyroid, iron, liver, kidney, diabetes, vitamin, inflammation, hormone, bone, cardiac, electrolyte, adrenal, PSA/prostate). Returns slug + name + marker count. Use mediora__explain_panel for the markers a panel contains.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mediora__list_symptoms ~79

List every patient-side symptom in the Mediora catalog (fatigue, joint pain, headache, etc.). Returns slug + short name. Use mediora__explain_symptom for the full triage-oriented explainer including the lab work-up a clinician would order.

NameTypeReqDescription
langstring–Language code. Defaults to 'en'.

No output schema declared.

No examples provided.

mediora__longitudinal_trend ~151

Return the per-marker trajectory analyser output for the authenticated patient — HbA1c rising, eGFR falling, ferritin depleting, etc. Each finding includes the marker slug, kind, severity (Info / Notice / Important), trend per year, sample count, date range and a supportive headline + detail. Proxies https://api.mediora.ai/api/trajectory/warnings with the user's token forwarded as Authorization: Bearer.

NameTypeReqDescription
bearer_tokenstringyesMediora.AI patient JWT. Get it by signing in at https://www.mediora.ai then copying localStorage.auth_token from DevTools, OR pass-through from a desktop client that stores Mediora credentials.

No output schema declared.

No examples provided.

mediora__lookup_marker ~131

Fuzzy-search markers by alias across EN/RU/HE. Useful when the upstream LLM has the lab's local name (e.g. "гликированный гемоглобин", "המוגלובין מסוכרר", "A1C") and needs to find the canonical Mediora slug.

NameTypeReqDescription
langstring–Preferred language for returned names. Defaults to 'en'.
querystringyesFree-text marker name in EN/RU/HE; e.g. 'A1C', 'гликированный', 'TSH', 'ויטמין D'.

No output schema declared.

No examples provided.

mediora__whoami ~131

Validate a Mediora.AI patient Bearer token and return the patient id + email it represents. Use this first to confirm the token before calling other auth-gated tools. The token is obtained by going through the standard Mediora.AI login at https://www.mediora.ai — the same JWT the browser stores in localStorage as 'auth_token'.

NameTypeReqDescription
bearer_tokenstringyesMediora.AI patient JWT. Get it by signing in at https://www.mediora.ai then copying localStorage.auth_token from DevTools, OR pass-through from a desktop client that stores Mediora credentials.

No output schema declared.

No examples provided.

Common questions

What is the io.github.SLAtech-IL/mediora-mcp server?

io.github.SLAtech-IL/mediora-mcp is listed in the public MCP registry as io.github.SLAtech-IL/mediora-mcp. Doctor-reviewed blood-test markers, conditions & symptoms as agent tools. EN/RU/HE. Hosted. This page covers its hosted endpoint (https://mcp.mediora.ai/mcp).

Is the io.github.SLAtech-IL/mediora-mcp server safe to use?

io.github.SLAtech-IL/mediora-mcp scores 77 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.github.SLAtech-IL/mediora-mcp server expose?

io.github.SLAtech-IL/mediora-mcp exposes 14 tools: mediora__list_markers, mediora__explain_marker, mediora__list_conditions, mediora__explain_condition, mediora__lookup_marker, and 9 more. Their descriptions and schemas cost roughly 1,678 tokens of context every time the server is loaded.

Does the io.github.SLAtech-IL/mediora-mcp server require authentication?

No. We connected to io.github.SLAtech-IL/mediora-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.SLAtech-IL/mediora-mcp server still maintained?

io.github.SLAtech-IL/mediora-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.