Otaghak
PYPI · OTAGHAK-MCP
Unofficial read-only Otaghak: search Iranian villas, availability, exact stay prices, reviews.
Available components
Last scanned (12 hours ago)
Scores higher than 63% of PyPI servers
Category E-commerce
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 Security50
- Malware scan not yet available for this package.Unverified
- 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 35 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 sepehr071/otaghak-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3644 tokens (~242/item across 15 items; 15 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 Management0
- Stability check failed: the tool surface changed between 0.1.4 and 0.3.1: 0 tool removals, 15 breaking changes, 0 additions. See how to fix → Fail
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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.
- 22 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.0 → 0.3.1 functional
- 19 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.3.0 functional
- 16 Oct 26 0
- Stability: unverified → fail ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.1.4 → 0.2.0 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
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 0
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.3 → 0.1.4 functional
- 12 Oct 26 49
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 22 Oct 2026 · Analysed pypi/otaghak-mcp@0.3.1
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 | sepehr071/otaghak-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sepehr071/otaghak-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 3390413315 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:15ac93e3466f6fa704338019fe9825e9b8bfbfc8fbb024776e1ade0aa30d4717 |
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 35 packages
| Packages resolved | 35 |
|---|---|
| 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 →
ot_deals Deals and discounts ~223
Current discounts: the home page's last-second deals and the most discounted stays (biggest percent first). last_second rooms are site-wide tonight-style deals shown 14:00-23:50 Iran time with undated prices; they are left out when `city` is given. most_discounted lists rooms of the 'discounted' collection (in `city` if given) that have a discount, sorted by percent; with dates the prices are for that stay. Next: ot_price_quote for the exact total.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | – | – | Arrival day YYYY-MM-DD, e.g. '2026-10-20' (not past, in the open calendar). |
| check_out | – | – | Departure day YYYY-MM-DD, e.g. '2026-10-23' (max 20 nights). |
| city | – | – | City slug, e.g. 'ramsar'. Default: whole site. |
| guests | – | – | Guests, e.g. 4; smaller rooms are left out. |
| limit | integer | – | Rooms per list. |
No output schema declared.
No examples provided.
ot_destinations Popular destinations and collections ~86
Popular cities and collections (themed landing pages: discounted, jungle villas, villas with pool, ...). Use when the user has no destination yet, or to find collection codes for ot_search_rooms `collection`. With `collection`, also lists the cities that collection covers (city slugs).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | – | – | Collection code to list its cities, e.g. 'beach'. |
No output schema declared.
No examples provided.
ot_find_place Find place or room code ~123
Turn a place name into the city / province slugs that ot_search_rooms needs, or a room code into its room. Cities come with their listing count (undated). A province `listings` number is not a search count. Room names are not searchable here: use ot_search_rooms with `name`. Next: ot_search_rooms, or ot_room for a room hit.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | City/province name (Persian or slug), e.g. 'رامسر', or a room code, e.g. '2508916'. |
No output schema declared.
No examples provided.
ot_help Help: rules and FAQ ~146
Read Otaghak's help center: the FAQ, or the guest terms (booking and cancellation rules, the five cancellation policies, refunds, wallet, check-in rules), host rules or quality policy. Without `query` you get every FAQ question (short answers) or the section titles of a page with a preview; with `query` the matching FAQ items or page paragraphs. A room's own cancellation policy is in ot_room.
| Name | Type | Req | Description |
|---|---|---|---|
| query | – | – | Persian words to look for, e.g. 'لغو', 'کیف پول'. |
| topic | string | – | faq, terms (booking, cancellation policies, refunds, wallet, stay rules), host_rules, quality_policy. |
No output schema declared.
No examples provided.
ot_holidays Holidays and weekdays ~133
List Iranian public holidays (Fridays included) in a date range, with Jalali dates and weekdays. Holiday flags are filled only about 7 weeks ahead: later days show no holidays, which means unknown, not working days. Use to plan around long weekends; weekend nights (Wed, Thu) and holidays usually cost more (see ot_room_calendar).
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Last day (inclusive), e.g. '2026-12-31'; max a year after start. |
| start | string | yes | First day YYYY-MM-DD, e.g. '2026-10-20'. |
No output schema declared.
No examples provided.
ot_host Host profile ~148
Check a host: response time, response and acceptance rates, member since, active rooms (undated starting prices) and the newest guest reviews across all their rooms. Pass host_id, or room_id to find the room's host. Use to judge whether a host is reliable or to see their other places.
| Name | Type | Req | Description |
|---|---|---|---|
| full_text | boolean | – | Return long texts in full instead of clipped. |
| host_id | – | – | Host id, e.g. 1626813. |
| reviews_limit | integer | – | Newest reviews across the host's rooms. |
| room_id | – | – | Or a room id, to find its host. |
| rooms_limit | integer | – | Host's rooms to list. |
No output schema declared.
No examples provided.
ot_late_checkout Late checkout ~135
Check whether a room offers late checkout, for how many hours and at what price (Toman, a unit not confirmed on the site), and with check_out whether it can be booked on that departure day (offered rooms are often closed for it on a given day). Use when the user wants to leave later than the check-out time. ot_price_quote adds it to a total with late_checkout_hours.
| Name | Type | Req | Description |
|---|---|---|---|
| check_out | – | – | Departure day to check, e.g. '2026-10-23'. |
| room_id | integer | yes | Room id (code), e.g. 2512254. |
No output schema declared.
No examples provided.
ot_price_quote Exact stay price ~266
Get the amount to pay (Toman) for a room, dates and guests: nights_total (the room page's payable amount for the base guests), the extra-guest charge, optional late checkout, and the total. `nightly` is the calendar breakdown (each discounted night is rounded to 1,000, so it can add up to a little more than nights_total; price_before_discount is absent when there is no discount). Also checks that every night is free, the stay length is allowed and the room takes that many guests (available=false with a reason otherwise). Late checkout that cannot be booked keeps the quote, with late_checkout.available=false. Use before the user books on otaghak.com.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | Arrival day YYYY-MM-DD, e.g. '2026-10-20'. |
| check_out | string | yes | Departure day, e.g. '2026-10-23' (max 20 nights). |
| guests | integer | yes | Guests, e.g. 4. |
| late_checkout_hours | – | – | Late checkout hours to add (offered rooms), e.g. 4. |
| room_id | integer | yes | Room id (code), e.g. 2512254. |
No output schema declared.
No examples provided.
ot_reviews Room reviews and rating ~141
Get a room's rating (0-5), star histogram, six category scores, percent of guests who recommend it, and written reviews, newest first (with host replies). rating is null and reviews empty when the room has no ratings yet (new rooms). Use after ot_room or ot_search_rooms to judge quality; ot_host has reviews across all of a host's rooms.
| Name | Type | Req | Description |
|---|---|---|---|
| full_text | boolean | – | Return long texts in full instead of clipped. |
| limit | integer | – | Reviews per page. |
| page | integer | – | Zero-based page. |
| room_id | integer | yes | Room id (code), e.g. 2512254. |
No output schema declared.
No examples provided.
ot_room Room details ~278
Get one room: description, capacity, rooms and beds, amenities, house rules, check-in/out times, cancellation policy, host, nearby places, approximate location, photos and nightly price. With check_in/check_out the price is the average night for those dates, even when they are booked (ot_price_quote or ot_room_calendar tells whether they are free); without, an undated starting price. instant_on_some_nights is the room-level flag: instant booking can differ per night, so for given dates read `instant` in ot_price_quote or ot_room_calendar. Use after ot_search_rooms or ot_find_place. Next: ot_price_quote (exact total), ot_room_calendar (free nights), ot_reviews, ot_host (host response and acceptance rates), ot_similar_rooms.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | – | – | Arrival day YYYY-MM-DD, e.g. '2026-10-20' (not past, in the open calendar). |
| check_out | – | – | Departure day YYYY-MM-DD, e.g. '2026-10-23' (max 20 nights). |
| full_text | boolean | – | Return long texts in full instead of clipped. |
| max_photos | integer | – | Photo URLs to return. |
| room_id | integer | yes | Room id (code), e.g. 2512254. |
No output schema declared.
No examples provided.
ot_room_calendar Room calendar ~179
Get a room's calendar day by day: nightly price after and before discount (Toman), free or booked, instant booking, min and max nights when arriving that day, weekend, public holiday, late checkout. A night is priced on its arrival day. Absent keys: price_before_discount = no discount, instant / weekend / holiday / late_checkout = no. Use to find free dates, cheap nights or allowed stay lengths. Next: ot_price_quote for a stay.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | Last day (inclusive), e.g. '2026-11-20'. Default: start + 30 days. |
| room_id | integer | yes | Room id (code), e.g. 2512254. |
| start | – | – | First day YYYY-MM-DD, e.g. '2026-10-20'. Default: today. |
No output schema declared.
No examples provided.
ot_search_filters Search filter codes ~163
List the search filters of a city, province or collection (or the whole site) with the codes ot_search_rooms takes. Returns the nightly price range (Toman), room types (ids for room_types), filter codes for `filters` (pool, jacuzzi, parking, heating, pets, parties, beach / jungle area, ...), and for a city its districts and landmarks (district_id). Use when the user asks for an amenity, a rule, a room type or a place near a landmark.
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | City slug, e.g. 'ramsar'; also returns its districts. |
| collection | – | – | Collection code, e.g. 'beach'. |
| province | – | – | Province slug, e.g. 'mazandaran'. |
No output schema declared.
No examples provided.
ot_search_rooms Search stays ~546
Search Otaghak stays (villas, cottages, apartments, eco-lodges) in a city, province or collection. With check_in/check_out every room is available on those dates and carries the stay price: price_per_night (average after discount) and stay_total for `guests` (incl. extra-guest charges; estimate, can be a few Toman off). Without dates prices are undated starting prices. Get slugs from ot_find_place, filter codes from ot_search_filters. Next: ot_room for details, ot_price_quote for the exact total, ot_room_calendar for other dates.
| Name | Type | Req | Description |
|---|---|---|---|
| bedrooms | – | – | Minimum bedrooms, e.g. 2. |
| check_in | – | – | Arrival day YYYY-MM-DD, e.g. '2026-10-20' (not past, in the open calendar). |
| check_out | – | – | Departure day YYYY-MM-DD, e.g. '2026-10-23' (max 20 nights). |
| city | – | – | City slugs from ot_find_place, e.g. ['ramsar'] (any of them). |
| city_tag | – | – | City theme slug with `city`, e.g. 'cottage' (ot_travel_guide). |
| collection | – | – | Collection code from ot_destinations, e.g. 'beach', 'villapool'. |
| district_id | – | – | Landmark district id from ot_search_filters, with `city`, e.g. 230. |
| filters | – | – | Codes from ot_search_filters exactly as returned, e.g. ['ruleValues=10101|10103|10102'] (pets). All must match. |
| guests | – | – | Guests, e.g. 4; smaller rooms are left out. |
| include_nearby | boolean | – | Also rooms around the city. |
| instant | boolean | – | Only instant booking. |
| limit | integer | – | Rooms per page. |
| max_price | – | – | Max nightly Toman after discount, e.g. 8000000. |
| min_price | – | – | Min nightly Toman after discount, e.g. 3000000. |
| min_rating | – | – | Minimum rating. |
| name | – | – | Room name words, e.g. 'نرگس'. |
| page | integer | – | Zero-based page. |
| prime | boolean | – | Only 'prime' rooms. |
| province | – | – | Province slug, e.g. 'mazandaran'. |
| rent_types | – | – | Rent type. |
| room_types | – | – | Room type ids from ot_search_filters, e.g. [138] villa. |
| sort | string | – | Order; with dates, cheapest re-sorts each page by stay_total. |
No output schema declared.
No examples provided.
ot_similar_rooms Similar rooms ~231
Get 4-5 alternatives to a room (same city and type), as the room page shows them (or, while that list is empty upstream, a search of the room's city and type up to 1.5x its price; `note` says so). Without dates prices are undated starting prices (not tonight's). With check_in/check_out the rooms are re-priced for that stay; rooms that are booked or too small for `guests` are listed in not_available. Use when the user's room is full or too expensive. Next: ot_room, ot_price_quote.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | – | – | Arrival day YYYY-MM-DD, e.g. '2026-10-20' (not past, in the open calendar). |
| check_out | – | – | Departure day YYYY-MM-DD, e.g. '2026-10-23' (max 20 nights). |
| guests | – | – | Guests, e.g. 4; smaller rooms are left out. |
| room_id | integer | yes | Room id (code), e.g. 2512254. |
No output schema declared.
No examples provided.
ot_travel_guide Destination travel guide ~189
Get the site's travel guide for a destination: guide text, the destination's FAQ (best season, sights, prices), related search pages (city themes such as beach, cottage, apartment with listing counts) and matching blog articles (restaurants, sights, souvenirs). Use when the user asks what a place is like or what to do there. City theme slugs from related_pages go to ot_search_rooms `city_tag`.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_query | – | – | Blog search words, e.g. 'رستوران رامسر'. Default: place name. |
| full_text | boolean | – | Return long texts in full instead of clipped. |
| kind | string | – | What `place` is. |
| max_chars | integer | – | Max characters of the guide text. |
| place | string | yes | City, province or collection slug, e.g. 'ramsar', 'beach'. |
No output schema declared.
No examples provided.
How do I install the Otaghak MCP server?
Otaghak runs locally as a PyPI package, launched with uvx otaghak-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 · otaghak-mcp
claude mcp add sepehr071-otaghak-mcp -- uvx otaghak-mcp
What is the Otaghak MCP server?
Otaghak is an MCP server listed in the public MCP registry as io.github.sepehr071/otaghak-mcp. Unofficial read-only Otaghak: search Iranian villas, availability, exact stay prices, reviews. This page covers its PyPI package (otaghak-mcp).
Is the Otaghak MCP server safe to use?
Otaghak scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 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 Otaghak MCP server expose?
Otaghak exposes 15 tools: ot_find_place, ot_search_rooms, ot_search_filters, ot_destinations, ot_deals, and 10 more. Their descriptions and schemas cost roughly 2,987 tokens of context every time the server is loaded.
Is the Otaghak MCP server still maintained?
Otaghak is still listed as active in the MCP registry. We last reached this channel on 22 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 Otaghak MCP server under?
Otaghak declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.