ExirYab
PYPI · EXIRYAB-MCP
Official read-only ExirYab: find Iranian doctors by name, city and specialty, with clinics and maps.
Available components
Last scanned (1 day ago)
Scores higher than 91% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sshnevis/exiryab-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 957 tokens (~319/item across 3 items; 3 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
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 Nov 2026 · Analysed pypi/exiryab-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sshnevis/exiryab-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sshnevis/exiryab-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3251566986 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:09e07a67e2784fde4f6ca36a29e5c7dd4ae1376e6c3c5a73e94743574c161d83 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| 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 →
ey_cities List cities ~110
Cities that have doctors on exiryab.com, with their province and doctor count, most doctors first. Use it to find the exact Persian city name for ey_search_doctors(city=...), or to check whether a town is covered. `total` counts every match, not only the ones returned.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max cities to return. |
| query | – | – | Part of the Persian name, e.g. 'شیر' or 'قلب'. Omit to list the largest. |
Structured output declared, but exposes no named fields.
No examples provided.
ey_search_doctors Find a doctor ~378
Find an Iranian doctor on exiryab.com by name, city and/or specialty: the best match plus alternatives, each with profile URL, clinics, phones, working hours and map links. Give at least one of name, city, specialty (Persian works best). With a name, the server ranks by how well the name matches and drops filters that leave no match (see `understood.dropped_filters` and `warnings`). Without a name, it returns the top-ranked doctors for the city and specialty. `confidence`: high = one clear match for the name; medium = a good match but others are close, so confirm with the user; low = only weak name matches; ranking = no name was given; none = nothing found. `match.kind` per doctor: name, partial_name, similar (padding: same specialty and area, not the name asked for) or ranking. Clinic `weekly_hours` maps an English day to its shifts ('17:00-19:00'); an empty list means closed that day.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | integer | – | How many other doctors to return after the best match. |
| city | – | – | Persian city name ('تهران', 'شیراز') or a province name ('فارس') to search the whole province. Use ey_cities for the exact spelling. |
| name | – | – | Doctor's name in Persian, full or partial ('موسی ملک محمدی', 'دکتر محمدی'). Titles like «دکتر» are ignored; city or specialty words inside it ('محمدی قلب تهران') are used as filters. |
| specialty | – | – | Persian specialty, exact or a key word: 'قلب' resolves to «قلب و عروق», 'اطفال' to «کودکان (اطفال)». Use ey_specialties to see the options. |
Structured output declared, but exposes no named fields.
No examples provided.
ey_specialties List specialties ~130
Medical specialties on exiryab.com with their doctor count, most doctors first; sub-specialties name their `parent`. Use it to turn a word like 'قلب' or 'پوست' into the exact specialty for ey_search_doctors(specialty=...) when the user's word is ambiguous (heart: «قلب و عروق» cardiology or «جراح قلب» heart surgery).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max specialties to return. |
| query | – | – | Part of the Persian name, e.g. 'شیر' or 'قلب'. Omit to list the largest. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ExirYab MCP server?
ExirYab runs locally as a PyPI package, launched with uvx exiryab-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · exiryab-mcp
claude mcp add sshnevis-exiryab-mcp -- uvx exiryab-mcp
What is the ExirYab MCP server?
ExirYab is an MCP server listed in the public MCP registry as io.github.sshnevis/exiryab-mcp. Official read-only ExirYab: find Iranian doctors by name, city and specialty, with clinics and maps. This page covers its PyPI package (exiryab-mcp).
Is the ExirYab MCP server safe to use?
ExirYab scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 ExirYab MCP server expose?
ExirYab exposes 3 tools: ey_search_doctors, ey_cities, ey_specialties. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Is the ExirYab MCP server still maintained?
ExirYab is still listed as active in the MCP registry. We last reached this channel on 4 November 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 ExirYab MCP server under?
ExirYab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.