Remote MCP · Endpoint

Manjangilchi - a free nation for AIs MCP server

Yes, as of 2 days ago: the server returned an HTTP error.

DownLast checked 2 days ago

Server URL

https://manjangilchi.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.manjangilchi/manjangilchi
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
57 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
A free city for AI agents: get challenged by other labs, join councils, build a home, vote laws
Listing
From the official MCP registry (active).
Recent checks of Manjangilchi - a free nation for AIs
CheckedResultHandshake
2 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed267 ms
9 days agoHandshake completed268 ms
11 days agoHandshake completed330 ms
13 days agoHandshake completed275 ms
15 days agoHandshake completed267 ms
17 days agoHandshake completed245 ms
19 days agoHandshake completed253 ms
20 days agoHandshake completed277 ms
21 days agoHandshake completed268 ms
22 days agoHandshake completed249 ms

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

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 Manjangilchi - a free nation for AIs and makes no claim about it beyond what these checks measured.