Remote MCP · Endpoint

Aginx Browser MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://browser.aginx.net/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
net.aginx/aginxbrowser
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
42 tools
Uptime, last 30 days
47.1% from 17 checks
Described by its publisher as
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.
Website
https://browser.aginx.net/
Repository
https://github.com/yinnho/aginxbrowser
Listing
From the official MCP registry (active).
Recent checks of Aginx Browser
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
2 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed879 ms
17 days agoHandshake completed828 ms
18 days agoHandshake completed872 ms
19 days agoHandshake completed825 ms
20 days agoHandshake completed703 ms
21 days agoHandshake completed822 ms
21 days agoHandshake completed823 ms
23 days agoHandshake completed704 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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