Remote MCP · Endpoint

Alexandria Archive MCP server

No. Alexandria Archive answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.alexandria-archive.com/mcp

The last check completed an MCP handshake.

Registry name
com.alexandria-archive/archive
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
559 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
History of Alexandria, Egypt: search the archive, read articles, find events and prints.
Listing
From the official MCP registry (active).
Recent checks of Alexandria Archive
CheckedResultHandshake
1 hour agoHandshake completed559 ms
8 days agoHandshake completed591 ms
9 days agoHandshake completed549 ms
11 days agoHandshake completed604 ms
12 days agoHandshake completed575 ms
12 days agoHandshake completed577 ms
14 days agoHandshake completed304 ms
14 days agoHandshake completed558 ms
16 days agoHandshake completed659 ms
19 days agoHandshake completed602 ms
21 days agoHandshake completed581 ms
24 days agoHandshake completed568 ms
26 days agoHandshake completed545 ms
28 days agoHandshake completed548 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Alexandria Archive and makes no claim about it beyond what these checks measured.