MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
Arabic Pipeline API 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.
What it does
Nine pay-per-call Arabic tools, no API key and no signup: text_metrics, text_normalize, text_detect_language, text_chunk, text_diff, text_search, audio_transcribe, doc_extract, doc_extract_batch.
Text — $0.002 a call ($0.005 for normalise): counts and reading time, Arabic/English/mixed detection with confidence, sentence-safe chunking with exact offsets, word-level diff after normalisation, and search that ignores tashkeel, alef/ya/ta-marbuta, hamza and Arabic-Indic digits.
Audio — $0.02: Arabic or English audio to clean text.
Documents — $0.03, or $0.10 for five in one call: structured fields from an Arabic PDF or image (receipts, invoices, IDs).
Billing is per call in USDC on Base over x402: the first request returns HTTP 402 with a PAYMENT-REQUIRED header, your client pays and repeats the same call. Contract and prices: https://arabic-pipeline.arabic-pipeline.workers.dev/openapi.json
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http arabic-pipeline-api-mcp https://arabic-pipeline-mcp.arabic-pipeline.workers.dev/
# 2 — ask your agent for something these tools do
# text_metrics, text_normalize, text_detect_language and 6 more
Arabic Pipeline API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http arabic-pipeline-api-mcp https://arabic-pipeline-mcp.arabic-pipeline.workers.dev/Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 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.
Measure text deterministically: characters, words, unique words, sentences, lines, paragraphs, digits, punctuation, average word and sentence length, reading time and an Arabic/Latin language mix. Works on any language, not only Arabic.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The text to measure. |
Canonicalise Arabic text for search, matching or indexing: remove tashkeel and tatweel, fold alef/ya/ta-marbuta, unify Arabic-Indic digits, strip bidi control characters and collapse whitespace. mode=light is lossless; search adds letter folding; index also strips punctuation so the result can be used as a dedup key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The Arabic text to normalize. |
| mode | string | no | light = whitespace/digits/bidi cleanup; search = + tashkeel removal and letter folding; index = + punctuation stripped. |
Identify whether text is Arabic, English, mixed or unknown from its script mix, with a confidence score and the count of Arabic, Latin and other letters. Deterministic and model-free, so it is cheap enough to run on every incoming message to route Arabic work.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The text to identify. |
Split long text into chunks for a model context window. Cuts at sentence boundaries when possible, then at word boundaries, and never mid-word unless a single word is longer than max_chars. Returns each chunk with exact start/end offsets into the original string plus an optional overlap for context carry-over.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The text to split. |
| max_chars | integer | no | Target maximum characters per chunk (default 1000). |
| overlap | integer | no | Characters of the previous chunk to repeat, snapped to a word start. At most half of max_chars. |
Compare two texts word by word after Arabic normalisation (tashkeel, alef/ya/ta-marbuta and digit variants are treated as equal). Returns an equal flag, a similarity score and the added and removed words. Use it for deduplication, re-import checks and QA of edited Arabic copy. Each side is limited to 1500 words.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | string | yes | The first text. |
| b | string | yes | The second text. |
Search Arabic (or any) text with normalisation: tashkeel, alef/ya/ta-marbuta, hamza and Arabic-Indic digit variants are ignored, so فَاطِمَة matches فاطمة and ١٢٣ matches 123. mode=words (default) matches whole words, phrase matches any substring, fuzzy tolerates up to max_distance edits per word. Returns exact start/end offsets into the original text plus a context snippet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The text to search (the corpus). |
| query | string | yes | What to look for; normalised like the corpus. |
| mode | string | no | words = whole-word phrase (default); phrase = any substring; fuzzy = edit-distance per word. |
| max_results | integer | no | Maximum matches to return. |
| context_chars | integer | no | Characters of context on each side of a match. |
| max_distance | integer | no | Edits allowed per word in fuzzy mode (default 1). |
Transcribe Arabic or English speech to plain text. Send the audio as base64 (webm, mp3, wav or mp4); the payload limit is 12 MB of base64. Returns the transcript plus the model that produced it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audio_base64 | string | yes | Base64-encoded audio file. |
| mime_type | string | no | Audio MIME type, e.g. audio/webm. |
Extract structured fields from an Arabic document image or PDF (receipts, invoices, official letters, national IDs, bank slips) as JSON: amounts, dates, names, identifiers and tax numbers, with null for fields the document does not contain. Send the file as base64 (jpeg, png or pdf); the limit is 12 MB of base64.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document_base64 | string | yes | Base64-encoded document image or PDF. |
| mime_type | string | no | Document MIME type, e.g. image/jpeg. |
Extract structured fields from 1 to 5 Arabic documents in one paid call: $0.10 for the batch, i.e. $0.02 per document instead of $0.03. Documents are processed independently and in parallel, results come back in request order with an echoed id, and one unreadable image does not fail the rest (it appears with ok=false and an error). Use this for a stack of receipts, invoices or bank slips.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| documents | array | yes | 1 to 5 documents, extracted independently and in parallel. |
| mime_type | string | no | Default MIME type for documents that omit their own. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Arabic Pipeline API or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| text_metrics | no tags | |
| text_normalize | no tags | |
| text_detect_language | no tags | |
| text_chunk | no tags | |
| text_diff | no tags | |
| text_search | no tags | |
| audio_transcribe | no tags | |
| doc_extract | no tags | |
| doc_extract_batch | 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
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
- Five new tools: text_detect_language, text_chunk, text_diff, text_search and doc_extract_batch. Same per-call prices ($0.002-$0.10); the OpenAPI contract and MCP server now report version 0.2.0.
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.
Any signed-in account that does not publish Arabic Pipeline API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.