Remote MCP · Endpoint

Arabic Pipeline API MCP server

No. Arabic Pipeline API answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://arabic-pipeline-mcp.arabic-pipeline.workers.dev/

The last check completed an MCP handshake.

Registry name
io.github.skypantherr/arabic-pipeline
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Pay-per-call Arabic text, audio and document utilities over x402. USDC on Base, no API key.
Listing
From the official MCP registry (active).
Recent checks of Arabic Pipeline API
CheckedResultHandshake
56 minutes agoHandshake completed216 ms
3 days agoHandshake completed224 ms
12 days agoHandshake completed298 ms
13 days agoHandshake completed334 ms
14 days agoHandshake completed203 ms
15 days agoHandshake completed272 ms
17 days agoHandshake completed228 ms
18 days agoHandshake completed280 ms
18 days agoHandshake completed143 ms
20 days agoHandshake completed198 ms
22 days agoHandshake completed131 ms
25 days agoHandshake completed272 ms
27 days agoHandshake completed230 ms

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

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 Pipeline API and makes no claim about it beyond what these checks measured.