Text & Number Toolkit
REMOTE · TEXTKIT.NOAHSARCH.TECH
Amounts in words (Arabic cheque grammar), number formatting, Arabic text tools, date parsing.
Available components
Last scanned (21 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2010 tokens (~167/item across 12 items; 10 tools + 2 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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.
- 4 Nov 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.
- 2 Nov 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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 67
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 4 Nov 2026 · Probed https://textkit.noahsarch.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noahsarch.tech | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 470026e1ea46ecc0e06d5a5a9df0965 |
| SANs: noahsarch.tech, *.noahsarch.tech | ||||||
| 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 textkit.noahsarch.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| noahsarch.tech. | 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://textkit.noahsarch.tech/mcp | Verified | 200 | |
| http (plaintext) | http://textkit.noahsarch.tech/mcp | Inconclusive | 406 |
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 →
amount_to_words Write a money amount in words ~258
Convert an amount in a currency to words for cheques, invoices and contracts, in 56 languages. Arabic output applies number–noun agreement (درهم واحد / درهمان / ثلاثة دراهم / أحد عشر درهماً) and the correct minor unit (فلس، هللة، قرش…); English uses CLDR currency names. style='cheque' adds the customary wrapper. Example: amount 1250.50, currency 'AED', language 'ar', style 'cheque'. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | yes | Amount as number or numeric string, e.g. 1234567.89 or '١٢٣٤٫٥٠'. |
| currency | string | yes | ISO 4217 code: AED, SAR, USD, EUR… |
| language | string | – | Language of the words: 'en', 'ar', 'fr', 'de', 'es', 'hi', 'ur'… (56 languages; list_languages). |
| style | string | – | cheque wraps the phrase the way cheques/contracts do ('… only' / 'فقط … لا غير'). |
Structured output declared, but exposes no named fields.
No examples provided.
convert_digits Convert digit systems ~108
Rewrite digits between Western (0-9), Arabic-Indic (٠-٩) and Persian/Urdu (۰-۹) anywhere in a text, leaving everything else untouched. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| to | string | yes | western 0-9 | arabic_indic ٠-٩ | persian ۰-۹. |
Structured output declared, but exposes no named fields.
No examples provided.
detect_script Detect scripts, direction and digit systems ~95
Proportions of writing systems in a text (latin, arabic, cyrillic, han…), dominant script, RTL/LTR direction, mixed-script flag, which digit systems appear, and hints such as Persian/Urdu-specific letters. Free. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
format_number Format a number for a locale ~244
Locale-correct display of a decimal, currency amount or percentage using CLDR rules: grouping (1,234,567 / 12,34,567 / 1.234.567 / 1 234 567), decimal mark, currency symbol placement, Arabic-Indic digits for ar_* locales. Example: number 1234567.891, locale 'en_IN', style 'currency', currency 'INR'. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | ISO 4217 code when style=currency. |
| decimals | – | – | Force a number of decimal places; default = locale/currency rule. |
| locale | string | yes | CLDR locale: 'en', 'en_IN' (lakh grouping), 'ar_AE' (Arabic-Indic digits), 'de_DE', 'fr_CH'… |
| number | – | yes | Number to format. |
| numbering | string | – | Digit system: locale default (ar_EG → Arabic-Indic, ar_AE → Western), or force latn / arab. |
| style | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_languages Supported languages and locales ~55
Languages available for words, the curated Arabic-grammar currencies, and notes on locales. Free. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
normalize_arabic Normalise Arabic text ~265
Clean Arabic text for matching, search and storage: strip diacritics and tatweel, unify alef forms, optional ة→ه and ى→ي, Western digits, Latin punctuation, whitespace. Reports exactly which rules changed the text. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| alef_maqsura_to_yaa | boolean | – | ى → ي (search normalisation; changes spelling). |
| collapse_whitespace | boolean | – | – |
| digits_to_western | boolean | – | ٠-٩/۰-۹ → 0-9. |
| punctuation_to_latin | boolean | – | ، ؛ ؟ ٪ ٫ ٬ → , ; ? % . , |
| strip_tashkeel | boolean | – | Remove diacritics (fatha, damma, shadda…). |
| strip_tatweel | boolean | – | Remove kashida/tatweel elongation. |
| taa_marbuta_to_haa | boolean | – | ة → ه (search normalisation; changes spelling). |
| text | string | yes | – |
| unify_alef | boolean | – | آ أ إ ٱ → ا. |
Structured output declared, but exposes no named fields.
No examples provided.
number_to_words Write a number in words ~160
Cardinal, ordinal or year wording of a number in 56 languages (en, ar, fr, de, es, pt, it, nl, tr, ru, hi, ur, id, ja, ko…). Example: number 2026, language 'en', to 'year' → 'twenty twenty-six'. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Target language code (56 supported). |
| number | – | yes | Number (integers or decimals; Arabic-Indic digits accepted). |
| to | string | – | cardinal (default) | ordinal (1st, الأول) | year (nineteen ninety-nine). |
Structured output declared, but exposes no named fields.
No examples provided.
parse_date Parse a human-written date (200 locales + Hijri) ~323
Turn a date written in natural language or local numeric formats into an ISO date/datetime: '3 mars 2026', '12.11.2026', 'next month', 'غداً', 'in 3 weeks', and Hijri dates such as '15 رمضان 1447' or '1 Muharram 1448' (converted by Umm al-Qura). Returns precision (day/month/year/time), the detected language and the relative base used. Pass languages and date_order when known. Example: text '١٥ رمضان ١٤٤٧'. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| date_order | – | – | Order for ambiguous numeric dates. Pass it whenever you know the source country. |
| languages | – | – | Language codes to try, e.g. ['en','ar','fr']. Strongly recommended for speed and accuracy. |
| prefer_future | boolean | – | Resolve ambiguous relative dates forward (deadlines) rather than backward. |
| relative_base | – | – | ISO datetime that relative phrases ('tomorrow', 'in 3 days') count from. Default: now. |
| text | string | yes | A date as humans write it: '3 mars 2026', '12/11/2026', 'غداً', 'in 3 weeks', '15 رمضان 1447', '2026-11-12T10:00'. |
| timezone | – | – | IANA zone for the result, e.g. 'Asia/Dubai'. |
Structured output declared, but exposes no named fields.
No examples provided.
parse_number Read a human-written number ~172
Turn '1.234,56', '١٬٢٣٤٫٥٦', '12 345,6' or '1,234.56' into an exact decimal, using the locale's separators first and a clearly flagged heuristic when they do not match. Example: text '1.234,56', locale 'de'. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale whose separators to assume first; a heuristic fallback handles mismatches and says so. |
| text | string | yes | Number as written by a human: '1.234,56', '١٬٢٣٤٫٥٦', '12 345,6', '1,234.56'. |
Structured output declared, but exposes no named fields.
No examples provided.
transliterate Romanise any script to ASCII ~132
Deterministic romanisation of any script to plain ASCII (Cyrillic, Greek, CJK, Devanagari, Thai, Arabic…) for slugs, sorting, matching and systems that reject non-ASCII. Not an official spelling: for Arabic names the result is a consonant skeleton and is flagged low confidence. Response: result plus data_confidence, estimated_items[], sources[], data_version, warnings[]; deterministic (no AI inside), nothing logged.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text in any script (Cyrillic, Greek, CJK, Arabic, Devanagari…). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Text & Number Toolkit MCP server?
Text & Number Toolkit is a hosted endpoint at https://textkit.noahsarch.tech/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 · textkit.noahsarch.tech
claude mcp add --transport http tech-noahsarch-text-number-toolkit 'https://textkit.noahsarch.tech/mcp'
What is the Text & Number Toolkit MCP server?
Text & Number Toolkit is an MCP server listed in the public MCP registry as tech.noahsarch/text-number-toolkit. Amounts in words (Arabic cheque grammar), number formatting, Arabic text tools, date parsing. This page covers its hosted endpoint (https://textkit.noahsarch.tech/mcp).
Is the Text & Number Toolkit MCP server safe to use?
Text & Number Toolkit scores 69 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 Text & Number Toolkit MCP server expose?
Text & Number Toolkit exposes 10 tools: amount_to_words, number_to_words, format_number, parse_number, convert_digits, and 5 more. Their descriptions and schemas cost roughly 1,812 tokens of context every time the server is loaded.
Does the Text & Number Toolkit MCP server require authentication?
No. We connected to Text & Number Toolkit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Text & Number Toolkit MCP server still maintained?
Text & Number Toolkit is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.