Remote MCP · Endpoint

io.github.cyanheads/met-museum-mcp-server MCP server

No. io.github.cyanheads/met-museum-mcp-server answered an MCP handshake 5 days ago.

UpLast checked 5 days ago

Server URL

https://met-museum.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/met-museum-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Search the Met collection, browse by department or update date, fetch full records and CC0 images.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/met-museum-mcp-server
CheckedResultHandshake
5 days agoHandshake completed263 ms
5 days agoHandshake completed301 ms
6 days agoHandshake completed287 ms
8 days agoHandshake completed269 ms
9 days agoHandshake completed267 ms
10 days agoHandshake completed286 ms
11 days agoHandshake completed283 ms
12 days agoHandshake completed290 ms
14 days agoHandshake completed288 ms
16 days agoHandshake completed277 ms
19 days agoHandshake completed269 ms
21 days agoHandshake completed292 ms
23 days agoHandshake completed260 ms
25 days agoHandshake completed115 ms
27 days agoHandshake completed128 ms
29 days agoHandshake completed92 ms
31 days agoHandshake completed86 ms
33 days agoHandshake completed122 ms
34 days agoHandshake completed105 ms

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

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 io.github.cyanheads/met-museum-mcp-server and makes no claim about it beyond what these checks measured.