_ registry / mcp streamable-http · checked 13h ago

arabic-pdf

https://rtlpdf.com

Registry code: f7477efa2001ec79

api record

Lays out Arabic, Urdu and Persian (Arabic-script) text as a correctly shaped, right-to-left PDF, and checks such text for problems that break PDFs and copy-paste. The tools do not write, translate or change wording.

endpoint
https://rtlpdf.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is arabic-pdf live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is arabic-pdf free to use?
Yes — the hub reached it with no key and no payment.
What tools does arabic-pdf have?
2 tools: make_pdf_arabic, check_arabic_text.
Is arabic-pdf safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
193ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • make_pdf_arabic unknown never probed

    Create a PDF from Arabic, Urdu or Persian text, or text that mixes them with English, with every letter correctly joined, lines running right to left, and numbers, dates, phone numbers and Latin words kept in order. Suited to PDFs, printable files, letters, notices, invoices, certificates, menus and handouts in Arabic, Urdu or Persian. The text is printed exactly as given; light Markdown is supported: '# ' headings, blank lines between paragraphs, '- ' bullets, '1. ' numbered lists, '| a | b |' tables (a '|---|' row marks a header) and **bold**. Returns a download link that works for 24 hours. It only lays out text: it does not write, translate or change wording, and it does not make images.

    mcp-tool

    {
      "type": "object",
      "title": "make_pdf_arabicArguments",
      "required": [
        "text"
      ],
      "properties": {
        "font": {
          "enum": [
            "auto",
            "naskh",
            "nastaliq",
            "cairo",
            "tajawal"
          ],
          "type": "string",
          "title": "Font",
          "default": "auto",
          "description": "'auto' picks Nastaliq for Urdu and Naskh otherwise. Cairo and Tajawal are modern sans styles."
        },
        "text": {
          "type": "string",
          "title": "Text",
          "maxLength": 30000,
          "minLength": 1,
          "description": "The full text to print, in Arabic, Urdu or Persian (English may be mixed in). Light Markdown allowed."
        },
        "bleed": {
          "type": "boolean",
          "title": "Bleed",
          "default": false,
          "description": "Add 3 mm bleed and crop marks for professional printing."
        },
        "paper": {
          "enum": [
            "A4",
            "A5",
            "Letter"
          ],
          "type": "string",
          "title": "Paper",
          "default": "A4",
          "description": "Page size."
        },
        "title": {
          "type": "string",
          "title": "Title",
          "default": "",
          "maxLength": 200,
          "description": "Document title for the PDF metadata and file name. Defaults to the first heading."
        },
        "justify": {
          "type": "boolean",
          "title": "Justify",
          "default": false,
          "description": "Justify paragraph lines."
        },
        "archival": {
          "type": "boolean",
          "title": "Archival",
          "default": false,
          "description": "Export as PDF/A-2a with PDF/UA-1 (archival and accessible), falling back to PDF/A-2b."
        },
        "language": {
          "enum": [
            "auto",
            "ar",
            "ur",
            "fa"
          ],
          "type": "string",
          "title": "Language",
          "default": "auto",
          "description": "Language of the text. 'auto' detects Urdu and Persian letters."
        },
        "font_size": {
          "anyOf": [
            {
              "type": "number",
              "maximum": 28,
              "minimum": 7
            },
            {
              "type": "null"
            }
          ],
          "title": "Font Size",
          "default": null,
          "description": "Text size in points, 7 to 28. Leave empty for the font's default."
        },
        "page_numbers": {
          "type": "boolean",
          "title": "Page Numbers",
          "default": true,
          "description": "Print page numbers when there is more than one page."
        }
      }
    }
    arguments 98 lines
  • check_arabic_text unknown 13h ago

    Check Arabic, Urdu or Persian text for problems that break PDFs, search and copy-paste: pre-shaped glyph characters and reversed letter order (typical of text copied out of a broken PDF), Persian or Urdu letters mixed into Arabic and the reverse, hidden direction-control characters, mixed digit systems, and characters the fonts cannot print. Returns the issues in English and Arabic and, when a safe fix exists, a fixed version of the text for the user to review. Deterministic rules; no AI.

    mcp-tool

    {
      "type": "object",
      "title": "check_arabic_textArguments",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "title": "Text",
          "maxLength": 200000,
          "minLength": 1,
          "description": "The text to check."
        },
        "language": {
          "enum": [
            "auto",
            "ar",
            "ur",
            "fa"
          ],
          "type": "string",
          "title": "Language",
          "default": "auto",
          "description": "Language of the text, or 'auto'."
        }
      }
    }
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f7477efa2001ec79.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f7477efa2001ec79/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f7477efa2001ec79/badge.svg)](https://brick.blue/agent/f7477efa2001ec79?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.