Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Parsi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
56
tools declared
local
runs on your machine
—
downloads a day
What it does
Offline Persian/Iran tools: Jalali dates, validators, Persian text, price inputs, RTL frontend.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user parsi-mcp '--' npx -y parsi-mcp
# 2 — ask your agent for something these tools do
# gregorian_to_jalali, jalali_to_gregorian, jalali_year_info and 53 more
Parsi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AMAll 1 server
amirjld1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Parsi as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user parsi-mcp '--' npx -y parsi-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
56 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Convert a Gregorian date to the Jalali (Persian) calendar.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | — |
| month | integer | yes | — |
| day | integer | yes | — |
Convert a Jalali (Persian) date to the Gregorian calendar.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | — |
| month | integer | yes | — |
| day | integer | yes | — |
Leap-year status and month length for a Jalali year.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | — |
| month | integer | no | — |
Validate an Iranian national ID (code melli) using its checksum.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Validate a 16-digit Iranian bank card number (Luhn).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Validate an Iranian Sheba (IBAN) number.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Validate and normalize an Iranian mobile number to 09xxxxxxxxx.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Normalize Arabic letter variants to Persian, clean spacing, and convert digits to Persian.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Convert any digits in a string to Persian digits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Write a non-negative integer in Persian words, e.g. for invoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | integer | yes | — |
Convert between rial and toman (1 toman = 10 rial).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | number | yes | — |
| from | string | yes | — |
| to | string | yes | — |
Identify the Iranian bank from a card number (first 6 digits / BIN).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| card | string | yes | — |
Identify the Iranian bank from a Sheba (IBAN) number (3-digit bank code).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sheba | string | yes | — |
Detect the mobile operator (MCI/Irancell/Rightel) of an Iranian mobile number.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Find the province of an Iranian landline number from its area code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Validate an Iranian 10-digit postal code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Convert Persian number words to a number, e.g. 'دویست و پنجاه هزار' -> 250000.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Format a Jalali date. Tokens: YYYY YY MMMM MM M DD D dddd.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pattern | string | no | — |
| persianDigits | boolean | no | — |
Parse text like '1403/05/09', '۱۴۰۳-۵-۹' or '9 مرداد 1403' into a Jalali date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Add days, months and/or years to a Jalali date (month overflow clamps to month length).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| months | integer | no | — |
| years | integer | no | — |
Days between two Jalali dates plus a Persian relative description.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | object | yes | — |
| to | object | yes | — |
Create a URL slug from Persian/Latin text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| separator | string | no | — |
Fix ZWNJ (half-space) for می/نمی and plural suffixes, Persian punctuation and spacing, Arabic letter variants.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
VAT helper. Rate (percent) must be supplied. mode 'exclusive' = amount excludes tax, 'inclusive' = amount includes tax.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | number | yes | — |
| ratePercent | number | yes | — |
| mode | string | yes | — |
Group digits in threes (200000 -> 200,000 or ۲۰۰٬۰۰۰). Accepts Persian/Arabic digits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
| digits | string | no | — |
| separator | string | no | — |
Strip separators and Persian/Arabic digits to a clean number, e.g. '۲۰۰٬۰۰۰' -> '200000'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Amount in Persian words with unit, e.g. 200000 toman -> 'دویست هزار تومان'. Toman may have one decimal digit (tenths = rials).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | string | yes | — |
| unit | string | no | — |
Ready-to-use RTL-friendly price input code: digit grouping while typing with caret preserved, live Persian words (aria-live), raw value submission. variant 'core' returns the shared helpers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| variant | string | yes | — |
Full RTL frontend guidelines for Persian/Arabic UIs (also available as prompt and resource 'rtl-frontend-guidelines').
No parameter schema on file.
Scan CSS/HTML/JSX/Tailwind text for LTR-only patterns (margin-left, ml-4, text-align:left, float:left, left/right, forced ltr, directional icons...) and suggest logical replacements.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | — |
Convert physical CSS (and React style objects) to logical properties.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| css | string | yes | — |
Convert Tailwind physical utilities to logical ones (ml-4 -> ms-4, pr-2 -> pe-2, text-left -> text-start).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Minimal RTL-ready setup for html, css, tailwind, nextjs, react or vue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | — |
Persian relative time like '۳ روز پیش' or '۲ ساعت دیگر'. Pass an ISO timestamp; 'now' defaults to the current time. Months = 30 days, years = 365 days.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timestamp | string | yes | — |
| now | string | no | — |
| persianDigits | boolean | no | — |
Calendar grid for a Jalali month (for date-pickers): weeks of 7 cells with day number, Gregorian date and Friday flag; null cells pad the edges. Default week starts Saturday.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | — |
| month | integer | yes | — |
| weekStart | string | no | — |
Start/end (Jalali and Gregorian) of the Jalali day, week (Saturday-Friday), month, quarter (season) or year containing a date. Use for reports and finance periods instead of Gregorian date libraries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | object | yes | — |
| period | string | yes | — |
Persian ordinal words: 3 -> سوم, 21 -> بیست و یکم, 30 -> سیام. 1 gives اول (set firstAsYekom for یکم).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | integer | yes | — |
| firstAsYekom | boolean | no | — |
Fuzzy-match a query against candidate strings, treating Arabic/Persian letter variants (ي/ی, ك/ک, آ/ا), diacritics, ZWNJ and digit styles as equal. Returns ranked matches with scores.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| candidates | array | yes | — |
| threshold | number | no | — |
| limit | integer | no | — |
Sort strings in Persian alphabetical order (ا ب پ ت ... ی). Digits first (numeric), then Persian, then Latin. Ignores ZWNJ and Arabic/Persian letter variants.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
| order | string | no | — |
Fix text typed with the wrong keyboard layout using the standard Iranian layout (ISIRI 9147): 'sghl' -> 'سلام', and Persian typed on English back to Latin. direction 'auto' picks by script.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| direction | string | no | — |
Validate an 11-digit Iranian legal-entity national ID (شناسه ملی شخص حقوقی / company ID) with its checksum.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
Build Excel/Sheets-safe CSV from rows: UTF-8 BOM, correct quoting, Persian digits in numeric cells converted to ASCII so Excel treats them as numbers, formula-injection guard, warnings for digit strings Excel may corrupt.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rows | array | yes | — |
| delimiter | string | no | — |
| bom | boolean | no | — |
| excelSafe | boolean | no | — |
CSS for Persian fonts (vazirmatn, shabnam, sahel, iransans): import link, font stack with fallbacks, RTL base styles. IRANSans is commercial so no CDN is given.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| font | string | yes | — |
| selector | string | no | — |
List Iran's 31 provinces with ISO 3166-2 code, Persian/English names and capital. Optional query matches Persian or English names (letter-variant tolerant).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
Character, letter, digit, ZWNJ, word, sentence and paragraph counts for Persian/mixed text, plus reading time. wordsPerMinute is an adjustable assumption (default 180).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| wordsPerMinute | number | no | — |
Detect text direction (first-strong and dominant script, mixed flag) and optionally wrap the text bidi-safely: Unicode isolates (FSI/RLI/LRI) or HTML <bdi> / dir=auto. Use for usernames, product names and mixed Persian/English strings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| wrap | string | no | — |
Truncate text to maxLength (ellipsis included) without breaking words, ZWNJ-joined words, surrogate pairs or diacritics. mode 'word' (default) or 'char'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| maxLength | integer | yes | — |
| ellipsis | string | no | — |
| mode | string | no | — |
Deterministic Persian placeholder text (seeded, original word list; not real prose) for mockups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| paragraphs | integer | no | — |
| sentencesPerParagraph | integer | no | — |
| wordsPerSentence | integer | no | — |
| seed | integer | no | — |
Display formats for an Iranian mobile (0912 345 6789, +98 912 345 6789, E.164) or landline (021-12345678). Accepts Persian digits, +98, 0098.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
| persianDigits | boolean | no | — |
Short Persian number form: 2500000 -> '۲٫۵ میلیون', 1200 -> '۱٫۲ هزار' (style 'latin' gives 2.5M). Optional unit like تومان.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | number | yes | — |
| style | string | no | — |
| persianDigits | boolean | no | — |
| maxFraction | integer | no | — |
| unit | string | no | — |
Decimals, percents and fractions in Persian words: '12.5' -> 'دوازده ممیز پنج دهم', percent adds درصد, fraction '3/4' -> 'سه چهارم'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
| mode | string | no | — |
| halfAsNim | boolean | no | — |
Age (years, months, days, total days) from a Jalali birth date. asOf defaults to today.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| birth | yes | Jalali date as {year,month,day} or text like '1405/07/24' | |
| asOf | no | Jalali date as {year,month,day} or text like '1405/07/24' |
Form validation for a Jalali date with readable reasons: month/day ranges (leap-aware), min, max and notFuture checks. Never throws.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | object | yes | — |
| min | no | Jalali date as {year,month,day} or text like '1405/07/24' | |
| max | no | Jalali date as {year,month,day} or text like '1405/07/24' | |
| notFuture | boolean | no | — |
Business-day helper: op 'is_business_day', 'add' (days may be negative) or 'count' (days after 'date' up to and including 'to'). Weekend is Friday (optionally Thursday too); supply holidays yourself or enable the fixed solar ones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| op | string | yes | — |
| date | yes | Jalali date as {year,month,day} or text like '1405/07/24' | |
| days | integer | no | — |
| to | no | Jalali date as {year,month,day} or text like '1405/07/24' |
Fixed solar-calendar public holidays of a Jalali year (Nowruz 1-4 Farvardin, 12-13 Farvardin, 14-15 Khordad, 22 Bahman, 29 Esfand) with Gregorian dates, plus the Hijri-based holiday list WITHOUT dates. Lunar holidays shift yearly and need the official annual calendar.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | — |
RTL frontend guidelines for Persian UIs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Parsi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.3.0 · scanned 19 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestc79a729de2fcf3c8f120899e9382a21e1d6f6ada6190156c559e4ed7ac572901
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (56 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| gregorian_to_jalali | no tags | |
| jalali_to_gregorian | no tags | |
| jalali_year_info | no tags | |
| validate_national_id | no tags | |
| validate_card_number | no tags | |
| validate_sheba | no tags | |
| normalize_mobile | no tags | |
| normalize_persian_text | no tags | |
| to_persian_digits | no tags | |
| number_to_persian_words | no tags | |
| convert_rial_toman | no tags | |
| bank_from_card | no tags | |
| bank_from_sheba | no tags | |
| mobile_operator | no tags | |
| landline_province | no tags | |
| validate_postal_code | no tags | |
| persian_words_to_number | no tags | |
| format_jalali_date | no tags | |
| parse_jalali_date | no tags | |
| jalali_add | no tags | |
| jalali_diff | no tags | |
| slugify_persian | no tags | |
| sanitize_persian_text | no tags | |
| calculate_vat | no tags | |
| format_number_grouped | no tags | |
| parse_grouped_number | no tags | |
| price_to_persian_words | no tags | |
| price_input_snippet | no tags | |
| rtl_guidelines | no tags | |
| rtl_audit_css | no tags | |
| rtl_convert_css | no tags | |
| rtl_convert_tailwind | no tags | |
| rtl_starter_snippet | no tags | |
| persian_relative_time | no tags | |
| jalali_month_grid | no tags | |
| jalali_period_range | no tags | |
| persian_ordinal | no tags | |
| persian_fuzzy_search | no tags | |
| persian_sort | no tags | |
| fix_keyboard_layout | no tags | |
| validate_legal_national_id | no tags | |
| csv_export_safe | no tags | |
| persian_font_preset | no tags | |
| iran_provinces | no tags | |
| persian_text_stats | no tags | |
| detect_text_direction | no tags | |
| truncate_persian_text | no tags | |
| persian_lorem_ipsum | no tags | |
| format_iran_phone | no tags | |
| format_short_number | no tags | |
| decimal_to_persian_words | no tags | |
| jalali_age | no tags | |
| validate_jalali_date | no tags | |
| iran_business_days | no tags | |
| iran_holidays | no tags | |
| parse_iran_address | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc79a729de2fcf3c8
Scanned2026-10-19
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.0. Pin a release below and the command asks for exactly that one.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Parsi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.