Remote MCP · Endpoint

City by Month MCP server

No. City by Month answered an MCP handshake 12 hours ago.

UpLast checked 12 hours ago

Server URL

https://mcp.citybymonth.com/

The last check completed an MCP handshake.

Registry name
com.citybymonth/citybymonth
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
4 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Read-only city climate normals, daylight and month-by-month data. Every answer cites its page.
Listing
From the official MCP registry (active).
Recent checks of City by Month
CheckedResultHandshake
12 hours agoHandshake completed69 ms
4 days agoHandshake completed121 ms
7 days agoHandshake completed62 ms

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

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 City by Month and makes no claim about it beyond what these checks measured.