Doktor
NPM · DOKTOR-MCP
Turkish health law for physicians: official legislation and high court decisions, source-grounded.
Available components
Last scanned (8 hours ago)
Scores higher than 50% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 117 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1044 tokens (~104/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 24 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.59.1 → 0.59.2 functional
- 22 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 9 Oct 26 39
First indexed and scored.
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 Oct 2026 · Analysed npm/doktor-mcp@0.59.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 117 packages
| Packages resolved | 117 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
classify_medical_legal_question ~117
Advanced/granular tool: prefer prepare_doctor_legal_information_pack for end-to-end questions; use this only when you specifically need medical-legal question classification in isolation. Classifies a physician question into legal dimensions (patient_rights, professional_ethics, criminal, privacy_kvkk, civil_compensation, etc.) and extracts search terms. Example: { "question": "Hasta onami olmadan mudahale edilirse ne olur?" }
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| sourceMode | string | – | – |
No output schema declared.
No examples provided.
drill_down_pack_item ~117
Follow-up tool — call ONLY after prepare_doctor_legal_information_pack. Pass the packId from that response plus a follow-up question mentioning a specific article number, law name, chamber, or decision number to retrieve just that item without rebuilding the pack. Example: { "packId": "pack-3f9a2c", "followUpQuestion": "madde 24 ne diyor?" }
| Name | Type | Req | Description |
|---|---|---|---|
| followUpQuestion | string | yes | – |
| pack | object | – | – |
| packId | string | – | – |
No output schema declared.
No examples provided.
filter_reasoned_precedents ~126
Advanced/granular tool: prefer prepare_doctor_legal_information_pack for end-to-end questions; use this only when you specifically need to filter/classify court decisions for reasoned analysis. Takes a list of decisions and filters them by eligibility (full text, legal reasoning, relevance). Optionally accepts a packId to operate on a previously prepared pack's decisions. Example: { "decisions": [...], "query": "hekim ihmal" }
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | array | – | – |
| packId | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
get_decision_full_text ~100
Fetch the full verbatim text of a single court decision by its documentId (from search_health_precedents or a pack's verifiedHighCourtPrecedents). Use for deep-dive into one decision instead of re-running the whole pack. Example: { "documentId": "yargitay:99001", "sourceMode": "live" }
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | – |
| sourceMode | string | – | – |
No output schema declared.
No examples provided.
get_legislation_provisions ~109
Advanced/granular tool: prefer prepare_doctor_legal_information_pack for end-to-end questions; use this only when you specifically need legislation provisions by document ID in isolation. Fetches full text of legislation provisions by document IDs. Example: { "documentIds": ["mevzuat:hastahaklari-yonetmelik:madde-5"], "sourceMode": "mock" }
| Name | Type | Req | Description |
|---|---|---|---|
| documentIds | array | yes | – |
| sourceMode | string | – | – |
No output schema declared.
No examples provided.
prepare_doctor_legal_information_pack ~188
PRIMARY ENTRY POINT — use this tool first for any physician legal question. Prepares a complete source-grounded legal information pack: classification, verbatim legislation provisions, verified high-court precedents, missing information, and lawyer review points. Returns a packId for follow-up drill-down. Set sourceMode:'live' to query official sources (mevzuat.gov.tr, Yargitay, Danistay); this is the default mode; sourceMode='mock' returns clearly-marked fixture data for testing only. Example: { "question": "Hasta tedaviyi reddederse hekimin sorumluluğu nedir?", "sourceMode": "live" }
| Name | Type | Req | Description |
|---|---|---|---|
| assessmentTone | string | – | – |
| includeDiagnostics | boolean | – | – |
| precedentSources | array | – | – |
| question | string | yes | – |
| sourceMode | string | – | – |
No output schema declared.
No examples provided.
search_health_legislation ~101
Advanced/granular tool: prefer prepare_doctor_legal_information_pack for end-to-end questions; use this only when you specifically need legislation search in isolation. Searches health-related legislation by keywords. Returns legislation titles, document IDs, and matched provisions. Example: { "searchTerms": ["hasta haklari", "tedaviyi red"], "sourceMode": "mock" }
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| sourceMode | string | – | – |
No output schema declared.
No examples provided.
search_health_precedents ~114
Advanced/granular tool: prefer prepare_doctor_legal_information_pack for end-to-end questions; use this only when you specifically need court precedent search in isolation. Searches health-related court decisions from Yargitay and Danistay. Returns decision summaries, document IDs, and relevance scores. Example: { "searchTerms": ["hekim sorumlulugu", "tedaviyi red"], "sourceMode": "mock" }
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| sourceMode | string | – | – |
No output schema declared.
No examples provided.
How do I install the Doktor MCP server?
Doktor runs locally as an npm package, launched with npx -y doktor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · doktor-mcp
claude mcp add afsozer-doktor-mcp -- npx -y doktor-mcp
What is the Doktor MCP server?
Doktor is an MCP server listed in the public MCP registry as io.github.afsozer/doktor-mcp. Turkish health law for physicians: official legislation and high court decisions, source-grounded. This page covers its npm package (doktor-mcp).
Is the Doktor MCP server safe to use?
Doktor scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. It declares no install or post-install scripts. 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 Doktor MCP server expose?
Doktor exposes 8 tools: classify_medical_legal_question, search_health_legislation, get_legislation_provisions, search_health_precedents, filter_reasoned_precedents, and 3 more. Their descriptions and schemas cost roughly 972 tokens of context every time the server is loaded.
Is the Doktor MCP server still maintained?
Doktor is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Doktor MCP server under?
Doktor declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.