Remote MCP · Endpoint

FarsiTools (paid) MCP server

No. FarsiTools (paid) answered an MCP handshake 29 minutes ago.

UpLast checked 29 minutes ago

Server URL

https://farsi-tools.johnaio281.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.johnaio281.farsi-tools/farsi-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
4.69 s
Tools exposed
27 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Persian and Iranian utilities for agents: Jalali dates, national ID, IBAN, holidays. Paid via x402.
Listing
From the official MCP registry (active).
Recent checks of FarsiTools (paid)
CheckedResultHandshake
29 minutes agoHandshake completed4.69 s
10 days agoHandshake completed2.60 s
11 days agoHandshake completed6.20 s
11 days agoHandshake completed2.55 s
13 days agoHandshake completed4.19 s
14 days agoHandshake completed2.03 s
15 days agoHandshake completed2.82 s
16 days agoHandshake completed61 ms
17 days agoHandshake completed2.91 s
19 days agoHandshake completed3.26 s
21 days agoHandshake completed4.45 s
24 days agoHandshake completed3.26 s
26 days agoHandshake completed56 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 FarsiTools (paid) and makes no claim about it beyond what these checks measured.