Remote MCP · Endpoint

Church Year MCP server

No. Church Year answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://crossandcovenant.co/api/mcp/church-year

The last check completed an MCP handshake.

Registry name
co.crossandcovenant/church-year
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Western church year: seasons, colors, feasts, Easter and Pascha, and the 1979 BCP Sunday lectionary.
Listing
From the official MCP registry (active).
Recent checks of Church Year
CheckedResultHandshake
1 hour agoHandshake completed103 ms
1 day agoHandshake completed800 ms
2 days agoHandshake completed763 ms
3 days agoHandshake completed75 ms
4 days agoHandshake completed170 ms
5 days agoHandshake completed186 ms
6 days agoHandshake completed219 ms
9 days agoHandshake completed77 ms
11 days agoHandshake completed119 ms
14 days agoHandshake completed127 ms
16 days agoHandshake completed543 ms
18 days agoHandshake completed91 ms
20 days agoHandshake completed160 ms
22 days agoHandshake completed94 ms
24 days agoHandshake completed152 ms

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

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