Remote MCP · Endpoint

net.barchin/mcp MCP server

No. net.barchin/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://barchin.net/mcp

The last check completed an MCP handshake.

Registry name
net.barchin/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
445 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Web scraping and Iranian-web data tools for AI agents: JS rendering, proxies, Markdown output.
Listing
From the official MCP registry (active).
Recent checks of net.barchin/mcp
CheckedResultHandshake
1 hour agoHandshake completed445 ms
6 hours agoHandshake completed404 ms
2 days agoHandshake completed450 ms
4 days agoHandshake completed654 ms
7 days agoHandshake completed440 ms
9 days agoHandshake completed409 ms
11 days agoHandshake completed416 ms
13 days agoHandshake completed444 ms
15 days agoHandshake completed417 ms
17 days agoHandshake completed414 ms
19 days agoHandshake completed409 ms
21 days agoHandshake completed394 ms
23 days agoHandshake completed417 ms
24 days agoHandshake completed618 ms
25 days agoHandshake completed408 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 net.barchin/mcp and makes no claim about it beyond what these checks measured.