Guide Registry is a remote MCP server that gives an AI agent 4 tools, among them get_guide, list_capabilities, list_guides. It answers at https://churchleader.guide/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Read-only Bicycle Guide registry: published guides, homes, taxonomy, capability spine. No auth.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_guide | Get one guide's registry row by slug, with its artifact + routing-surface status. Inputs: slug |
list_capabilities | Traverse the capability spine joining books, guides (capability packages), KSAO-grade elements and jobs. Use min_guides=2 for the cross-cutting capabilities that span many guides, role=<role> for what a job requires, capability_detail=<slug Inputs: min_guides, has_job, role, capability, conflicting, ksao_type |
list_guides | List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plus the distribution roll-up (including guides homed to a property with no rendering surface). Inputs: home, status, access, standard, guide_type, domain |
list_taxonomy | Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, and the classification conventions (pillar/spoke, discriminant home, bicycle-guide-serves-all) as machine-readable data rather than |
Every block below points at https://churchleader.guide/mcp. Pick your client and copy.
claude mcp add --transport http guide-registry https://churchleader.guide/mcp
{
"mcpServers": {
"guide-registry": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://churchleader.guide/mcp"]
}
}
}{
"mcpServers": {
"guide-registry": {
"url": "https://churchleader.guide/mcp"
}
}
}{
"servers": {
"guide-registry": {
"type": "http",
"url": "https://churchleader.guide/mcp"
}
}
}{
"context_servers": {
"guide-registry": {
"url": "https://churchleader.guide/mcp"
}
}
}{
"mcpServers": {
"guide-registry": {
"serverUrl": "https://churchleader.guide/mcp"
}
}
}{
"mcpServers": {
"guide-registry": {
"url": "https://churchleader.guide/mcp"
}
}
}name: Guide Registry
version: 0.0.1
schema: v1
mcpServers:
- name: Guide Registry
type: streamable-http
url: https://churchleader.guide/mcp{
"mcpServers": {
"guide-registry": {
"httpUrl": "https://churchleader.guide/mcp"
}
}
}{
"mcpServers": {
"guide-registry": {
"type": "http",
"url": "https://churchleader.guide/mcp"
}
}
}{
"mcpServers": {
"guide-registry": {
"url": "https://churchleader.guide/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fchurchleader.guide%2Fmcp&type=streamable_http&id=guide-registry&name=Guide%20Registry
It answered our last check on 19 October 2026 in 445 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by churchleader.guide and served from churchleader.guide, the vendor's own domain: https://churchleader.guide/mcp.
4, as returned by the server's own tools/list on 11 September 2026: get_guide, list_capabilities, list_guides, list_taxonomy.
It answered our last check on 19 October 2026 in 445 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://churchleader.guide/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: guide.churchleader. Endpoint host: churchleader.guide. ARD identifier: urn:air:guide.churchleader:mcp:guide-registry.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.