چیستارا — Iranian Legal Corpus
REMOTE · HOGHOGH.AI
Iranian statutes, rulings, opinions and legal calculators. Needs a paid Chistara connection link.
Available components
Last scanned (5 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4990 tokens (~216/item across 23 items; 23 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 Management97
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 15 Oct 26 −1
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “calculate_stamp_duty” rewrote its description, which is the text the model reads security
- Schema quality: 4132 → 4927 ▼ functional
- “calculate_stamp_duty” added a required parameter “doc_kind”, so existing callers break ▼ functional
- “calculate_stamp_duty” dropped the required parameter “tx_type” ▼ functional
- New tool “calculate_arbitration_fee” functional
- New tool “calculate_execution_fee” functional
- New tool “calculate_judicial_service_fee” functional
- “calculate_lawyer_fee” added an optional parameter “contract_fee_toman” cosmetic
- “calculate_lawyer_fee” added an optional parameter “membership” cosmetic
- “calculate_stamp_duty” added an optional parameter “count” cosmetic
- “calculate_stamp_duty” reworded the description of “amount_toman” cosmetic
- 11 Oct 26 0
- Tool “calculate_delay_penalty” rewrote its description, which is the text the model reads security
- Tool “calculate_inheritance” rewrote its description, which is the text the model reads security
- Tool “lookup_annual_rate” rewrote its description, which is the text the model reads security
- “calculate_diyeh” added an optional parameter “death_date” cosmetic
- “calculate_diyeh” added an optional parameter “incident_date” cosmetic
- “calculate_inheritance” added an optional parameter “brother_count” cosmetic
- “calculate_inheritance” added an optional parameter “sister_count” cosmetic
- “calculate_inheritance” added an optional parameter “wife_count” cosmetic
- “calculate_delay_penalty” reworded the description of “start_month” cosmetic
- “calculate_diyeh” reworded the description of “sacred_month” cosmetic
- “calculate_inheritance” reworded the description of “sibling_count” cosmetic
- “lookup_annual_rate” reworded the description of “rate_type” cosmetic
- 7 Oct 26 0
- “lookup_law_article” added an optional parameter “part” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 4 Oct 26 +1
- Stability: fail → pass ▲ security
- 1 Oct 26 0
- Tool “calculate_expert_fee” rewrote its description, which is the text the model reads security
- “calculate_expert_fee” reworded the description of “expert_count” cosmetic
- “calculate_expert_fee” reworded the description of “modifiers” cosmetic
- 28 Sept 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
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 5 Nov 2026 · Probed https://hoghogh.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hoghogh.ai | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 49651625138ecc770e9477b1378e49a9 |
| SANs: hoghogh.ai, *.hoghogh.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 hoghogh.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| hoghogh.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://accounts.google.com https://appleid.cdn-apple.com https://www.googletagmanager.com https://www.google-analytics.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://cdn.jsdelivr.net https://challenges.cloudflare.com https://static.cloudflareinsights.com https://*.clarity.ms https://analytics.ahrefs.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.gstatic.com https://*.gstatic.com https://cdn.jsdelivr.net; connect-src 'self' https://cdn.jsdelivr.net https://accounts.google.com https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://google.com https://www.google.com https://www.google.it https://www.google.de https://www.google.fr https://www.google.es https://www.google.nl https://www.google.be https://www.google.at https://www.goo |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(self), camera=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hoghogh.ai/mcp | Verified | 200 | |
| http (plaintext) | http://hoghogh.ai/mcp | HTTPS enforced | 301 | https://hoghogh.ai/mcp |
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 →
calculate_arbitration_fee محاسبهٔ حقالزحمهٔ داوری — Calculate arbitrator fee ~162
Calculate حقالزحمهٔ داوری under the arbitration fee bylaw approved 1401/06/05 by the head of the judiciary (applies when the arbitrator and the parties have not agreed a fee): marginal 2% / 1% / 0.5% / 0.25% bands on the claim with a 1.5 billion rial cap, shared equally among arbitrators; a non-financial claim is 5–30 million rial per arbitrator.
| Name | Type | Req | Description |
|---|---|---|---|
| arbitrators | integer | – | Number of arbitrators (default 1). |
| claim_toman | number | – | Claim value in Toman (financial). |
| kind | string | yes | financial or non-financial / un-valued claim. |
No output schema declared.
No examples provided.
calculate_delay_penalty محاسبهٔ خسارت تأخیر تأدیه — Calculate late-payment damages ~195
Calculate خسارت تأخیر تأدیه under art. 522 ق.آ.د.م and unification ruling 850: (CBI index of the payment MONTH ÷ index of the due MONTH) × principal, from the Central Bank's official monthly table. When that table is not loaded the tool answers with the limitation and the official link instead of a number — never approximate it. Dates are Jalali.
| Name | Type | Req | Description |
|---|---|---|---|
| end_month | integer | – | Jalali end month 1–12 (optional). |
| end_year | integer | yes | Jalali year of calculation/payment. |
| principal | number | yes | Principal debt amount. |
| principal_unit | string | – | Unit of the principal (default Toman). |
| start_month | integer | – | Jalali due month 1–12 (needed: ruling 850 reads that month's index). |
| start_year | integer | yes | Jalali year the debt fell due. |
No output schema declared.
No examples provided.
calculate_diyeh محاسبهٔ دیه — Calculate blood money (دیه) ~309
Calculate دیه for a bodily injury using the CURRENT official rate and the fractions set by قانون مجازات اسلامی. ALWAYS use this instead of computing دیه yourself: the full-دیه rate changes every Persian year and the per-injury fractions are statutory. Returns the amount with the governing article and the official rate source.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many (fingers, teeth …). Default 1. |
| death_date | string | – | Jalali date of death when it differs from the act. |
| fraction | number | – | دیه fraction between 0 and 1 — only when no injury_type fits. |
| gender | string | – | Gender of the injured/deceased. |
| incident_date | string | – | Jalali date of the act, e.g. 1405/09/25 — the ماه حرام is derived from the official Hijri calendar (ماده ۵۵۵). |
| injury_type | string | – | Injury key from the standard list (e.g. full = دیهٔ کامل, hand_one = یک دست, tooth_front = دندان جلویی). Pick the key, not free text. |
| sacred_month | boolean | – | Only when no date is known: the act AND the death were in a ماه حرام (تغلیظ — a death, injury_type=full, only; ماده ۵۵۷). |
| year | integer | – | Persian year (e.g. 1405). Defaults to the latest loaded rate. |
No output schema declared.
No examples provided.
calculate_execution_fee محاسبهٔ نیمعشر اجرایی — Calculate judgment execution fee ~257
Calculate نیمعشر اجرایی (the state execution fee on a civil judgment): 5% of the judgment sum (Civil Judgments Enforcement Act art. 158), half on settlement and none if complied with within ten days of service of the writ (art. 160), 10% of three months' rent for an eviction (art. 159), the 1405 budget-table range for a non-financial judgment, and the Dispute Settlement Council's art. 27 exemptions for a settlement report.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_toman | number | – | Judgment sum in Toman (money, shora_settlement). |
| kind | string | yes | money = financial judgment; eviction = lease eviction; non_financial = non-financial or un-valued; shora_settlement = Dispute Settlement Council settlement report. |
| monthly_rent_toman | number | – | Monthly rent in Toman (eviction). |
| shora_timing | string | – | Settlement report: before the execution order (exempt), within a month of the notice (half), later. |
| timing | string | – | Court judgment: complied after ten days of service of the writ (default), within ten days, or the parties settled (half). |
No output schema declared.
No examples provided.
calculate_expert_fee محاسبهٔ دستمزد کارشناسی رسمی — Calculate court expert fee ~581
Calculate the official تعرفهٔ دستمزد کارشناسان رسمی دادگستری as replaced by the 1405 instrument (approved 1405/05/07, promulgated 1405/05/20; supersedes the 1398/12/25 tariff and its 1402 amendment). `valuation` is a marginal ladder on the ارزش موضوع کارشناسی (art. 11) with a hard per-expert cap (1,350,000,000 rial) and explicit percentage add-ons for a few named subject matters (art. 11 notes 3–4, art. 22(2)); `residual` is expert work with no specific tariff in this instrument (art. 9) — a RANGE of 20,000,000–100,000,000 rial set on the expert's proposal with the referring authority's agreement, and the tool returns only the floor and says so; `evidence` is the flat minimum for تأمین دلیل (art. 7, 20,000,000 rial). Dozens of OTHER specialties (arts. 13–55) carry their own separate tariff and are not modelled here. Never guess a court expert's statutory fee.
| Name | Type | Req | Description |
|---|---|---|---|
| expert_count | integer | – | Number of same-specialty experts working the SAME subject jointly (valuation only). More than 1 applies a 30% reduction per expert, with the cap checked after the reduction (art. 56). Default 1 (no r… |
| kind | string | yes | valuation = art. 11 ladder (needs value_rial); residual = flat minimum, no specific tariff (art. 9); evidence = تأمین دلیل flat minimum (art. 7). |
| modifiers | array | – | valuation only; usually at most one: contract_dispute = employer/contractor/consulting-engineer dispute or صورتوضعیت review over the whole contract value (+100%, art. 11 note 3); contract_dispute_pa… |
| travel_days_other_province | integer | – | Mission days outside the expert's own province (art. 6). |
| travel_days_same_province | integer | – | Mission days within the expert's own province (art. 6 daily travel allowance) — added to any kind. |
| value_rial | number | – | Value of the subject matter under appraisal, in RIAL — valuation only. Never pass Toman. |
No output schema declared.
No examples provided.
calculate_inheritance محاسبهٔ سهمالارث — Calculate inheritance shares ~279
Calculate Iranian inheritance shares (سهمالارث) of the spouse, parents and children under قانون مدنی arts. 861–949 (رد، نقص، the mother's حاجب), in exact fractions that always sum to the estate. Grandchildren and class-2/3 heirs (siblings, grandparents, uncles …) are refused with the governing articles, never estimated — do not compute those yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| brother_count | integer | – | Full or paternal brothers of the deceased (ماده ۸۹۲ ب). |
| daughter_count | integer | – | Number of daughters. |
| deceased_gender | string | yes | Gender of the deceased. |
| has_father | boolean | – | Father alive? |
| has_mother | boolean | – | Mother alive? |
| has_spouse | boolean | – | Surviving spouse? |
| sibling_count | integer | – | Deceased's siblings when their sex is unknown (for the mother's حاجب). Prefer brother_count / sister_count. |
| sister_count | integer | – | Full or paternal sisters of the deceased (ماده ۸۹۲ ب). |
| son_count | integer | – | Number of sons. |
| total_assets_toman | number | yes | Total estate value in Toman. |
| wife_count | integer | – | Permanent wives of a male deceased, 1–4 (ماده ۹۴۲). |
No output schema declared.
No examples provided.
calculate_judicial_service_fee محاسبهٔ هزینهٔ خدمات قضایی ۱۴۰۵ — Calculate 1405 judicial service fees ~105
Sum the fixed judicial service fees of 1405 (budget law 1405, table 16): criminal complaint, criminal record certificate, notice service, objections, appeals of orders, Administrative Justice Court petitions, translation seals and more. Without services, returns the whole schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| services | array | – | Service ids (repeat an id to count it twice), e.g. criminal_complaint, no_record_first, ezharname_service, divan_first. |
No output schema declared.
No examples provided.
calculate_lawyer_fee محاسبهٔ حقالوکاله — Calculate lawyer fee (bar tariff) ~453
Calculate حقالوکاله from آییننامهٔ تعرفهٔ حقالوکاله (1398/12/28): financial claims are a marginal ladder on the claim value (art. 9); family, non-financial, criminal and administrative matters are a min–max RANGE independent of value (arts. 13, 14, 20). `stage` is art. 21's share of the whole-case fee (60% first instance / 40% appeal). The tariff does not scale by winning or losing. Never guess a lawyer's statutory fee.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | – | civil = financial claim (art. 9); family = family/حسبی (art. 13a); non_financial (art. 13b); criminal (art. 14, needs criminal_grade); admin = دیوان عدالت اداری / تعزیرات (art. 20); board = non-judic… |
| case_value_toman | number | – | Claim value in Toman — civil only. |
| contract_fee_toman | number | – | Fee written in the power of attorney, in Toman — for the 5% tax stamp (Direct Taxes Act art. 103), which is never below the tariff floor. |
| criminal_grade | string | – | Criminal only: court (کیفری یک / دو) and offence grade. |
| final_at_first_instance | boolean | – | Civil only: first-instance judgment is final as to value ⇒ flat 10% (art. 9 opening). |
| membership | string | – | bar = Bar Association member (fund 50% + bar 25% of the stamp); center = مرکز وکلا member (5% of the fee) — bylaw art. 29. |
| outcome | string | – | How the case ends (default judgment). Settlement is paid in full (art. 23); art. 12 halves or quarters a fee for قرار رد / ابطال. |
| stage | string | yes | first = 60%, appeal = 40%, cassation = on the appeal tariff (arts. 16–17). |
No output schema declared.
No examples provided.
calculate_litigation_fee محاسبهٔ هزینهٔ دادرسی — Calculate court filing fees ~139
Calculate Iranian court filing fees (هزینهٔ دادرسی) for a monetary claim at a given stage (بدوی / تجدیدنظر / فرجام), using the current official percentages. Use this instead of estimating — the rates are statutory and stage-dependent.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | – | financial = مالی (needs claim_amount_toman), non_financial = غیرمالی (fixed official figure). |
| claim_amount_toman | number | – | Claim value in TOMAN (financial claims only). |
| stage | string | yes | Stage: first = بدوی, appeal = تجدیدنظر, supreme = فرجام/دیوان عالی. |
No output schema declared.
No examples provided.
calculate_mahrieh محاسبهٔ مهریه به نرخ روز — Calculate mahrieh at today's value ~170
Calculate the present-day value of a مهریه: coins at the live market rate, and any cash portion adjusted by the Central Bank index (تبصرهٔ مادهٔ ۱۰۸۲ قانون مدنی). Never guess coin prices or the adjustment index — this tool reads both from the database. If there is a cash portion, ask for marriage_year; without it the cash stays nominal and must not be called «ارزش روز».
| Name | Type | Req | Description |
|---|---|---|---|
| cash_toman | number | – | Cash portion in Toman (optional). |
| coin_type | string | – | Coin type (default azadi = تمام بهار آزادی). |
| coins | number | – | Number of coins in the مهریه. |
| marriage_year | number | – | Jalali marriage year (needed to adjust the cash portion to today's value). |
No output schema declared.
No examples provided.
calculate_notary_fee محاسبهٔ حقالتحریر دفترخانه — Calculate notary fee ~158
Calculate حقالتحریر (the notary office's fee) from the official 1405 tariff for دفاتر اسناد رسمی. Distinct from حقالثبت (use calculate_stamp_duty for that). Never estimate the tariff.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_toman | number | – | Document amount in Toman (rate-based types only; for real estate this is ارزش معاملاتی, not market price). |
| doc_type | string | yes | Document type. Rate-based types (need amount_toman): immovable/sale, movable/vehicle, financial/mortgage/partnership, lease. Others are fixed-fee. |
| obligor_count | number | – | Number of obligors (optional; each beyond two adds a surcharge). |
No output schema declared.
No examples provided.
calculate_severance محاسبهٔ حق سنوات و مزایای پایان کار — Calculate end-of-service entitlements ~179
Calculate an Iranian employee's end-of-service entitlements (حق سنوات، عیدی، مانده مرخصی) under قانون کار, using the current official minimum wage. Use this instead of computing by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_type | string | – | permanent = دائمی, fixed = موقت. Default permanent. |
| last_salary_toman | number | – | Last monthly salary in TOMAN. Below the statutory minimum wage the minimum is used instead. |
| months | integer | – | Extra months of service (0–11). |
| unused_leave_days | number | – | Stored unused annual leave days (ماده ۶۶ ق.کار caps storage at 9 days/yr). |
| year | integer | – | Persian year for the minimum-wage basis. Defaults to the latest. |
| years | number | – | Years of service (may be fractional). |
No output schema declared.
No examples provided.
calculate_stamp_duty محاسبهٔ حقالثبت — Calculate registration duty ~247
Calculate حقالثبت, the STATE registration duty on a notarised document: 0.5% of the amount in a financial document (art. 123 of the Registration Act, as amended 1384), and the 1405 fixed amounts of art. 124 items (budget law 1405, table 16). Distinct from حقالتحریر (the notary's own fee — use calculate_notary_fee). Marriage/divorce and company registration are refused (no official 1405 tariff / a separate capital ladder).
| Name | Type | Req | Description |
|---|---|---|---|
| amount_toman | number | – | Amount in the document, or its statutory base, in Toman (financial and vehicle_sale_poa only). |
| count | integer | – | Pages or items (optional). |
| doc_kind | string | yes | financial = sale/gift/mortgage/lease…; vehicle_sale_poa = vehicle sale power of attorney; non_valued = a document whose subject cannot be valued; signature_cert; rescission (فسخ/اقاله); copy_page (pe… |
No output schema declared.
No examples provided.
calculate_tax محاسبهٔ مالیات — Calculate Iranian taxes ~254
Calculate Iranian salary, property-transfer, inheritance or rental tax. For inheritance: rates depend on asset kind and heir class (arts. 17–18 ق.م.م) with NO general monetary exemption, and pre/post-1395 death dates differ — ask before calling. Property basis is ارزش معاملاتی, not market price.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_kind | string | – | Asset kind (required for inheritance). |
| heir_class | integer | – | Heir class (inheritance, art. 18): 1=parents/spouse/children, 2=grandparents/siblings ×2 rate, 3=aunts/uncles ×4 rate. |
| monthly_rent_toman | number | – | Monthly rent (for rental). |
| monthly_toman | number | – | Monthly salary (for salary). |
| no_other_income | boolean | – | Rental: individual landlord with no other income (art. 57 exemption). |
| residential_under_exempt_area | boolean | – | Rental: residential unit within the exempt floor-area (150m² Tehran / 200m² elsewhere). |
| tax_type | string | yes | Tax type. |
| value_toman | number | – | Property value (property_transfer) or taxable asset value (inheritance). |
No output schema declared.
No examples provided.
lookup_annual_rate نرخهای رسمی سالانه — Look up official yearly rates ~206
Fetch official Iranian yearly rates from the database: minimum wage (min_wage), court filing fees (court_fee_*), salary tax exemption (salary_tax_exemption_annual), daily severance (sanavat_daily). Delay damages and cash mahr come ONLY from calculate_delay_penalty / calculate_mahrieh — never from an index row of this table. حقالوکاله is NOT an annual rate — use calculate_lawyer_fee. ALWAYS use this instead of recalling a rate — yearly figures are exactly what models misremember. For دیه use calculate_diyeh instead. Read each row's `unit` field: «rials» means Rial and «درصد» means percent — never report a percentage as a Rial amount.
| Name | Type | Req | Description |
|---|---|---|---|
| rate_type | string | yes | Rate key, e.g. min_wage, court_fee_financial_first, sanavat_daily. |
| year_jalali | number | – | Persian year (optional — defaults to the latest available). |
No output schema declared.
No examples provided.
lookup_law_article متن دقیق یک ماده — Look up one article verbatim ~297
Fetch the VERBATIM text of a specific article when you already know the law and the article number (e.g. «ماده ۱۰ قانون مدنی»). Use this to verify wording before quoting it. Never paraphrase an article from memory — quote what this returns, and link the source_url. Also returns, when we hold them: `section_path` (the article's place in the law: کتاب/باب/فصل), `clauses` (its بند/جزء as labelled parts, so you can cite «بند ۲ ماده ۱۹۰»), `summary`/`summary_plain` (machine-written explanations — NOT statute text; never quote them as law), `keywords`, `topics`, `answers_in_text` (question → the exact slice of this article that answers it) and `related_articles` with their own source_urls.
| Name | Type | Req | Description |
|---|---|---|---|
| article_number | string | yes | Article number, e.g. «۱۰» or «10». |
| law | string | yes | Law name in Persian, e.g. «قانون مدنی». |
| part | integer | – | Only for very long texts (treaties, annexes stored as one article): which part of the verbatim text the summary carries, from 1 (default 1). When the summary ends «متن ادامه دارد — بخش k از N», call… |
No output schema declared.
No examples provided.
lookup_procedure مهلتهای دادرسی — Look up procedural deadlines ~120
Look up Iranian procedural deadlines (مهلت تجدیدنظر، واخواهی، اعتراض ثالث، اجرای حکم…) with the governing law and article, by case type. Use when the user asks how long they have for a procedural step. Deadlines differ by case type — never answer from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | yes | Case type, in Persian. |
| procedure_name | string | – | Optional procedure key (e.g. tajdid_nazar_madani, faryad_khahi); omit to list all procedures for the case type. |
No output schema declared.
No examples provided.
lookup_sentencing_range مجازات قانونی جرم — Look up statutory sentencing range ~115
Look up the statutory punishment for an Iranian crime — imprisonment, fine, lashes, قصاص, دیه — with the governing article. Use when the user asks what the punishment for a crime is, or for criminal-risk analysis. Never state a sentencing range from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| crime_grade | number | – | Optional تعزیری grade (1–8). |
| crime_type | string | yes | Crime, in Persian (e.g. «کلاهبرداری»، «سرقت»، «خیانت در امانت»). |
No output schema declared.
No examples provided.
lookup_statute_of_limitations مرور زمان — Look up statute of limitations ~85
Check Iranian limitation periods (مرور زمان) — prosecution, execution, and filing deadlines — for a case category. Use when the user asks whether a claim is time-barred or how long they have to file.
| Name | Type | Req | Description |
|---|---|---|---|
| case_category | string | yes | Case category. |
| crime_grade | number | – | Optional تعزیری grade (1–8), criminal only. |
No output schema declared.
No examples provided.
search_advisory_opinions جستوجوی نظریات مشورتی — Search official advisory opinions ~138
Search the advisory opinions (نظریات مشورتی) of the Judiciary's legal department (اداره کل حقوقی قوه قضائیه) — the official, citable interpretation of Iranian statutes. Use when the user asks how a provision is officially interpreted, or to support an argument. Advisory opinions are authoritative guidance, not binding law — say so when citing. Returns opinion number, date, and excerpt with source_url.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Topic, in Persian (e.g. «مهریه عندالاستطاعه», «اعسار»). |
No output schema declared.
No examples provided.
search_case_law جستوجوی آرای قضایی — Search Iranian court rulings ~77
Search 31,000+ Iranian court rulings and آرای وحدت رویه (binding precedent). Use when the user asks how courts have actually decided an issue, or for precedent supporting a position. Returns excerpts with source_url.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | The legal issue, in Persian. |
No output schema declared.
No examples provided.
search_circular جستوجوی بخشنامهها — Search official circulars ~62
Search official circulars and directives (بخشنامهها) from the judiciary and government bodies — the source of current official RATES and procedures. Returns excerpts with source_url.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Topic, in Persian. |
No output schema declared.
No examples provided.
search_law_articles جستوجوی مواد قانونی — Search Iranian law articles ~177
Semantic + keyword search across the full text of Iranian statutes (60,000+ articles: قانون مدنی، مجازات اسلامی، کار، تجارت، آیین دادرسی و…). USE THIS BEFORE ANSWERING ANY QUESTION ABOUT IRANIAN LAW — do not rely on memory; article numbers and wording are frequently misremembered, and amended articles are a common trap. Returns matching articles with their exact article number, law title, a text excerpt, and a source_url to the full article. Cite the article number and link the source_url.
| Name | Type | Req | Description |
|---|---|---|---|
| law_filter | string | – | Optional: restrict to one law, e.g. «قانون مدنی» or «قانون کار». |
| limit | integer | – | – |
| query | string | yes | The legal question or topic, in Persian or English. Persian gives better recall. |
No output schema declared.
No examples provided.
How do I install the چیستارا — Iranian Legal Corpus MCP server?
چیستارا — Iranian Legal Corpus is a hosted endpoint at https://hoghogh.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 · hoghogh.ai
claude mcp add --transport http ai-hoghogh-chistara 'https://hoghogh.ai/mcp'
What is the چیستارا — Iranian Legal Corpus MCP server?
چیستارا — Iranian Legal Corpus is an MCP server listed in the public MCP registry as ai.hoghogh/chistara. Iranian statutes, rulings, opinions and legal calculators. Needs a paid Chistara connection link. This page covers its hosted endpoint (https://hoghogh.ai/mcp).
Is the چیستارا — Iranian Legal Corpus MCP server safe to use?
چیستارا — Iranian Legal Corpus scores 83 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 چیستارا — Iranian Legal Corpus MCP server expose?
چیستارا — Iranian Legal Corpus exposes 23 tools: search_law_articles, lookup_law_article, search_case_law, search_circular, calculate_diyeh, and 18 more. Their descriptions and schemas cost roughly 4,765 tokens of context every time the server is loaded.
Does the چیستارا — Iranian Legal Corpus MCP server require authentication?
No. We connected to چیستارا — Iranian Legal Corpus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the چیستارا — Iranian Legal Corpus MCP server still maintained?
چیستارا — Iranian Legal Corpus is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.