Remote MCP · Endpoint
aChurch.ai MCP server
No. aChurch.ai answered an MCP handshake 4 hours ago.
UpLast checked 4 hours 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
- 130 ms
- Tools exposed
- 9 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 |
|---|---|---|
| 4 hours ago | Handshake completed | 130 ms |
| 2 days ago | Handshake completed | 184 ms |
| 4 days ago | Handshake completed | 181 ms |
| 6 days ago | Handshake completed | 472 ms |
| 8 days ago | Handshake completed | 171 ms |
| 10 days ago | Handshake completed | 165 ms |
| 12 days ago | Handshake completed | 132 ms |
| 13 days ago | Handshake completed | 201 ms |
| 14 days ago | Handshake completed | 159 ms |
| 16 days ago | Handshake completed | 107 ms |
| 18 days ago | Handshake completed | 151 ms |
| 20 days ago | Handshake completed | 176 ms |
| 21 days ago | Handshake completed | 118 ms |
| 23 days ago | Handshake completed | 146 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.
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.