Remote MCP · Endpoint

Arabic Name Calligraphy MCP server

No. Arabic Name Calligraphy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://arabickeyboard.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.arabickeyboard/name-calligraphy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Writes names in Arabic script with alternative spellings, six calligraphy styles and PNG artwork.
Listing
From the official MCP registry (active).
Recent checks of Arabic Name Calligraphy
CheckedResultHandshake
1 hour agoHandshake completed82 ms
1 day agoHandshake completed117 ms
2 days agoHandshake completed111 ms
3 days agoHandshake completed822 ms
4 days agoHandshake completed80 ms
5 days agoHandshake completed114 ms
6 days agoHandshake completed97 ms
9 days agoHandshake completed170 ms
11 days agoHandshake completed73 ms
14 days agoHandshake completed104 ms
16 days agoHandshake completed118 ms
18 days agoHandshake completed78 ms
20 days agoHandshake completed86 ms
22 days agoHandshake completed699 ms
24 days agoHandshake completed225 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Arabic Name Calligraphy and makes no claim about it beyond what these checks measured.