Remote MCP · Endpoint

UN Charter 1945 MCP server

Yes, as of 8 hours ago: the server returned an HTTP error.

DownLast checked 8 hours ago

Server URL

https://mcp.arxo.io/mcp/charter

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

Registry name
io.arxo/charter
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
21 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
UN Charter (1945, as amended) as an executable model with worked cases; not UN-affiliated
Listing
From the official MCP registry (active).
Recent checks of UN Charter 1945
CheckedResultHandshake
8 hours agoFailed - the server returned an HTTP error—
10 days agoHandshake completed314 ms
11 days agoHandshake completed310 ms
11 days agoHandshake completed331 ms
13 days agoHandshake completed309 ms
15 days agoHandshake completed374 ms
15 days agoHandshake completed336 ms
16 days agoHandshake completed502 ms
17 days agoHandshake completed310 ms
19 days agoHandshake completed315 ms
22 days agoHandshake completed345 ms
24 days agoHandshake completed306 ms
26 days agoHandshake completed327 ms
29 days agoHandshake completed307 ms

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

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