Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FarsiTools (paid)

REMOTE · FARSI-TOOLS.JOHNAIO281.WORKERS.DEV

Persian and Iranian utilities for agents: Jalali dates, national ID, IBAN, holidays. Paid via x402.

+4 this week 65 Trust /100

Last scanned (11 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2658 tokens (~98/item across 27 items; 27 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% 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; "fa_fixRtl" implies "remove" 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 28 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
Changelog

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.

  • 5 Nov 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.

  • 3 Nov 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.

  • 1 Nov 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.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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://farsi-tools.johnaio281.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=johnaio281.workers.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 63a205b5eddc3fa8d66a145340e3bf8795d
SANs: *.johnaio281.workers.dev, johnaio281.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of farsi-tools.johnaio281.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://farsi-tools.johnaio281.workers.dev/mcp Verified 200
http (plaintext) http://farsi-tools.johnaio281.workers.dev/mcp Served over HTTP 200
MCP tools · 27 exposed · ~2,613 tokens

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 →

Tool Tokens
fa_amountToWords ~93

Write an amount of Iranian rial or toman out in Persian words (مبلغ به حروف), as required on Iranian cheques, invoices and contracts. Use it to render a payable amount for a Persian-speaking payer. Returns the amount spelled in Persian words with its unit. ($0.005 per call, USDC on Base)

NameTypeReqDescription
amount–yes–
number–––
unitstring––

No output schema declared.

No examples provided.

fa_digits ~99

Convert the digits inside a string between Persian (۰-۹), Arabic-Indic (٠-٩) and ASCII (0-9) numeral systems, leaving the rest of the text untouched. Use it to make Persian text machine-readable or to render an ASCII number in Persian script. Returns the converted string. ($0.003 per call, USDC on Base)

NameTypeReqDescription
textstringyestext containing digits
tostring––

No output schema declared.

No examples provided.

fa_fixRtl ~98

Remove Unicode bidi control characters and repair the spacing around right-to-left punctuation. Use it to clean Persian or Arabic text that renders in the wrong order or shows stray markers. Returns the cleaned string. ($0.005 per call, USDC on Base)

NameTypeReqDescription
options––optional, e.g. {"digits":"ascii"}
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_gregorianToJalali ~119

Convert a Gregorian (ISO, Western) calendar date to the Jalali, Solar Hijri, Persian or Shamsi calendar used in Iran. Use it to display a date to Iranian users, to schedule work in the Iranian calendar, or to convert a Gregorian deadline into a Jalali date. Returns the Jalali year, month, day and month name. ($0.005 per call, USDC on Base)

NameTypeReqDescription
daynumberyes–
monthnumberyes–
yearnumberyes–

No output schema declared.

No examples provided.

fa_iranCity ~94

Look up an Iranian city by its Persian name and return the province it belongs to. Use it to resolve a city in an address or to group a location by region. Returns the city and its province. ($0.005 per call, USDC on Base)

NameTypeReqDescription
namestring–city name in Persian
textstring–alias for name
valuestring–alias for name

No output schema declared.

No examples provided.

fa_iranHolidayCheck ~99

Check whether a given Jalali (Solar Hijri) date is an Iranian public holiday and return the holiday's name if it is. Use it before booking, scheduling or sending a deadline-sensitive action on an Iranian working day. Returns whether it is a holiday and which one. ($0.005 per call, USDC on Base)

NameTypeReqDescription
daynumberyes–
monthnumberyes–
yearnumberyes–

No output schema declared.

No examples provided.

fa_iranHolidays ~80

Return the official Iranian public holidays for a Jalali (Solar Hijri) year, with each holiday's Gregorian date and name. Use it to plan delivery or support schedules around Iranian holidays, or to flag non-working days. Returns the holiday list. ($0.005 per call, USDC on Base)

NameTypeReqDescription
yearnumberyes–

No output schema declared.

No examples provided.

fa_iranProvince ~105

Look up an Iranian province by its Persian name and return its capital and major cities. Use it to resolve a province in an address, to attach geographic context to a user, or to normalize a location field. Returns the province, its capital and its cities. ($0.005 per call, USDC on Base)

NameTypeReqDescription
namestring–province name in Persian
textstring–alias for name
valuestring–alias for name

No output schema declared.

No examples provided.

fa_iranProvinces ~62

List all 31 Iranian provinces with their capitals and major cities. Use it to populate a province dropdown, to build a location picker, or to validate a region name. Returns every province. ($0.003 per call, USDC on Base)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fa_jalaliToGregorian ~119

Convert a Jalali (Solar Hijri, Persian, Shamsi) calendar date to the Gregorian calendar. Use it to turn a date written in the Iranian calendar back into an ISO 8601 date, to check whether a Jalali date is today, or to compare an Iranian deadline with a Western one. Returns the Gregorian year, month, day and weekday. ($0.005 per call, USDC on Base)

NameTypeReqDescription
daynumberyes–
monthnumberyes–
yearnumberyes–

No output schema declared.

No examples provided.

fa_keywords ~110

Extract the frequent keywords from Persian text, filtering Persian and English stopwords and ranking by frequency. Use it to build a search index, an automatic tag list, or a topic summary for a Persian document. Returns the ranked keywords. ($0.01 per call, USDC on Base)

NameTypeReqDescription
limitnumber––
options––optional, e.g. {"digits":"ascii"}
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_normalize ~121

Normalize Persian (Farsi) text: convert Arabic letter variants (ي, ك) to their Persian forms, unify ZWNJ and spacing, and map Arabic-Indic digits to Persian digits. Use it before indexing, searching or comparing Persian text so that lookalike spellings match. Returns the normalized string. ($0.01 per call, USDC on Base)

NameTypeReqDescription
options––optional, e.g. {"digits":"ascii"}
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_numberToWords ~89

Write an integer out in Persian words (عدد به حروف), for example 1234 as هزار و دویست و سی و چهار. Use it for Persian invoices, cheque amounts, legal and official forms, and display. Returns the number spelled in Persian words. ($0.01 per call, USDC on Base)

NameTypeReqDescription
number–yesinteger, string digits, commas or Persian digits

No output schema declared.

No examples provided.

fa_rialToman ~83

Convert an amount between Iranian rial and toman, where 1 toman equals 10 rial. Use it when a price is given in one unit and must be shown or billed in the other. Returns the converted amount. ($0.003 per call, USDC on Base)

NameTypeReqDescription
amount–yes–
number–––
unitstring––

No output schema declared.

No examples provided.

fa_sentences ~106

Split Persian text into sentences, handling the Persian question mark ؟, the exclamation mark, ellipsis … and abbreviation boundaries. Use it to chunk Persian text for summarization, translation or per-sentence processing. Returns the list of sentences. ($0.005 per call, USDC on Base)

NameTypeReqDescription
options––optional, e.g. {"digits":"ascii"}
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_similarity ~88

Measure the similarity of two Persian strings as a trigram Jaccard score from 0 to 1. Use it to detect near-duplicate Persian text, deduplicate a corpus, or rank one Persian string against another. Returns the similarity score. ($0.01 per call, USDC on Base)

NameTypeReqDescription
astringyesfirst string
bstringyessecond string

No output schema declared.

No examples provided.

fa_stats ~106

Measure Persian text: character count, word count, line count and the number of ZWNJ half-space characters. Use it to size a Persian document, enforce a length limit, or report text statistics for Persian content. Returns a stats object. ($0.005 per call, USDC on Base)

NameTypeReqDescription
options––optional, e.g. {"digits":"ascii"}
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_stripHtml ~100

Strip HTML tags and decode HTML entities out of a string, leaving the readable text behind. Use it to clean web pages or scraped content before feeding it to an agent or an index. Returns the plain text. ($0.005 per call, USDC on Base)

NameTypeReqDescription
options––optional, e.g. {"digits":"ascii"}
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_transliterate ~130

Transliterate Persian, Dari or Arabic script into Latin letters, optionally as a URL slug. Use it to index Persian text in a Latin-keyword search engine, to build slugs for Persian titles, or to render Persian names in a Latin-only system. Returns the Latin transliteration and, when asked, the slug. ($0.01 per call, USDC on Base)

NameTypeReqDescription
options––optional, e.g. {"digits":"ascii"}
slugboolean––
textstringyesPersian (Farsi) text or value to process. Max 100000 characters.

No output schema declared.

No examples provided.

fa_validateBankCard ~90

Validate an Iranian bank card number, called a PAN (کارت بانکی), with the Luhn check digit, and return the issuing bank. Use it before charging a card or accepting card details from a customer. Returns validity, the masked number and the bank name. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyes16-digit Iranian bank card number

No output schema declared.

No examples provided.

fa_validateCompanyId ~90

Validate an Iranian company national ID (شناسه ملی اشخاص حقوقی, the 11-digit legal-entity identifier) by recomputing its check digit. Use it when onboarding a business customer or validating an Iranian legal entity. Returns validity and the parsed digits. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyes11-digit legal-entity national ID

No output schema declared.

No examples provided.

fa_validateEconomicCode ~82

Validate an Iranian economic code (کد اقتصادی, the 12-digit taxpayer identifier) by recomputing its check digit. Use it when validating the tax identifier on an Iranian invoice or a supplier record. Returns validity and the parsed digits. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyes12-digit economic code

No output schema declared.

No examples provided.

fa_validateLandline ~97

Validate and normalize an Iranian landline number with its area code (021 for Tehran and so on) and resolve that area code to a city. Use it to verify a fixed-line contact or to route a support request to the right region. Returns validity, the normalized number, the area code and the city. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyeslandline in any common format

No output schema declared.

No examples provided.

fa_validateMobile ~96

Validate and normalize an Iranian mobile phone number, checking the operator prefix (MCI, Irancell, Rightel, Shatel) and the national format 09xxxxxxxxx. Use it to verify a phone number on a sign-up form or before sending an SMS. Returns validity, the normalized number and the operator. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyesmobile in any common format

No output schema declared.

No examples provided.

fa_validateNationalId ~87

Validate an Iranian national ID (کد ملی, code melli) by recomputing its check digit. Use it before accepting an identity number from a form, a customer, or an API payload. Returns whether the number is valid, and the parsed digits. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyes10-digit national ID

No output schema declared.

No examples provided.

fa_validatePostalCode ~82

Validate an Iranian postal code (کد پستی, the 10-digit code) by recomputing its check digit. Use it before using a postal code for delivery or address validation. Returns validity, the normalized code and its province. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyes10-digit postal code

No output schema declared.

No examples provided.

fa_validateSheba ~88

Validate an Iranian IBAN, called Sheba (شبا), with the ISO 13616 mod-97 check, and return the bank code. Use it before sending or crediting an Iranian bank transfer. Returns validity, the normalized IBAN and the bank identifier. ($0.005 per call, USDC on Base)

NameTypeReqDescription
valuestringyesIR + 24 digits

No output schema declared.

No examples provided.

Install

How do I install the FarsiTools (paid) MCP server?

FarsiTools (paid) is a hosted endpoint at https://farsi-tools.johnaio281.workers.dev/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 · farsi-tools.johnaio281.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-johnaio281-farsi-tools-farsi-tools 'https://farsi-tools.johnaio281.workers.dev/mcp'
Common questions

What is the FarsiTools (paid) MCP server?

FarsiTools (paid) is an MCP server listed in the public MCP registry as dev.workers.johnaio281.farsi-tools/farsi-tools. Persian and Iranian utilities for agents: Jalali dates, national ID, IBAN, holidays. Paid via x402. This page covers its hosted endpoint (https://farsi-tools.johnaio281.workers.dev/mcp).

Is the FarsiTools (paid) MCP server safe to use?

FarsiTools (paid) scores 65 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 FarsiTools (paid) MCP server expose?

FarsiTools (paid) exposes 27 tools: fa_normalize, fa_transliterate, fa_stats, fa_digits, fa_numberToWords, and 22 more. Their descriptions and schemas cost roughly 2,613 tokens of context every time the server is loaded.

Does the FarsiTools (paid) MCP server require authentication?

No. We connected to FarsiTools (paid) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FarsiTools (paid) MCP server still maintained?

FarsiTools (paid) 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.