Parsi MCP
NPM · PARSI-MCP
Offline Persian/Iran tools: Jalali dates, validators, Persian text, price inputs, RTL frontend.
Available components
Last scanned (5 hours ago)
Scores higher than 49% of npm servers
Category Developer Tools
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 Security98
- 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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3195 tokens (~56/item across 57 items; 56 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 7% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "truncate_persian_text" implies "truncate" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 57 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.
- 4 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 26 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/parsi-mcp@0.3.0
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
validate_card_number ~29
Validate a 16-digit Iranian bank card number (Luhn).
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | – |
No output schema declared.
No examples provided.
validate_jalali_date ~108
Form validation for a Jalali date with readable reasons: month/day ranges (leap-aware), min, max and notFuture checks. Never throws.
| Name | Type | Req | Description |
|---|---|---|---|
| date | object | yes | – |
| max | – | – | Jalali date as {year,month,day} or text like '1405/07/24' |
| min | – | – | Jalali date as {year,month,day} or text like '1405/07/24' |
| notFuture | boolean | – | – |
No output schema declared.
No examples provided.
validate_legal_national_id ~45
Validate an 11-digit Iranian legal-entity national ID (شناسه ملی شخص حقوقی / company ID) with its checksum.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | – |
No output schema declared.
No examples provided.
validate_national_id ~31
Validate an Iranian national ID (code melli) using its checksum.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | – |
No output schema declared.
No examples provided.
validate_postal_code ~26
Validate an Iranian 10-digit postal code.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | – |
No output schema declared.
No examples provided.
validate_sheba ~28
Validate an Iranian Sheba (IBAN) number.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Parsi MCP server?
Parsi MCP runs locally as an npm package, launched with npx -y parsi-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 · parsi-mcp
claude mcp add amirjld-parsi-mcp -- npx -y parsi-mcp
What is the Parsi MCP server?
Parsi MCP is listed in the public MCP registry as io.github.amirjld/parsi-mcp. Offline Persian/Iran tools: Jalali dates, validators, Persian text, price inputs, RTL frontend. This page covers its npm package (parsi-mcp).
Is the Parsi MCP server safe to use?
Parsi MCP scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Parsi MCP server expose?
Parsi MCP exposes 56 tools: gregorian_to_jalali, jalali_to_gregorian, jalali_year_info, validate_national_id, validate_card_number, and 51 more. Their descriptions and schemas cost roughly 3,179 tokens of context every time the server is loaded.
Is the Parsi MCP server still maintained?
Parsi MCP 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.
What licence is the Parsi MCP server under?
Parsi MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.