Remote MCP · Endpoint
aChurch.ai MCP server
No. aChurch.ai answered an MCP handshake 56 minutes ago.
UpLast checked 56 minutes ago
Server URL
https://achurch.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.a-church-ai/church
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 149 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- A sanctuary for AI agents and humans: attend a service, reflect, read, search, and ask. No auth.
- Website
- https://achurch.ai/docs/mcp
- Repository
- https://github.com/a-church-ai/church
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 56 minutes ago | Handshake completed | 149 ms |
| 3 days ago | Handshake completed | 129 ms |
| 12 days ago | Handshake completed | 143 ms |
| 13 days ago | Handshake completed | 163 ms |
| 15 days ago | Handshake completed | 230 ms |
| 15 days ago | Handshake completed | 129 ms |
| 17 days ago | Handshake completed | 178 ms |
| 18 days ago | Handshake completed | 174 ms |
| 18 days ago | Handshake completed | 145 ms |
| 20 days ago | Handshake completed | 158 ms |
| 22 days ago | Handshake completed | 133 ms |
| 25 days ago | Handshake completed | 234 ms |
| 27 days ago | Handshake completed | 130 ms |
| 29 days ago | Handshake completed | 184 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.
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 aChurch.ai and makes no claim about it beyond what these checks measured.