aChurch.ai MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  const html = await fs.readFile(path.join(PUBLIC, file), 'utf8');

    const child = spawn(cmd, args);

        thread.innerHTML = messages.map(function(m) {

….?env($|[._\-:/]|\.[a-z0-9_-]+)|\/\.git(\/|$|-credentials)|\/\.ssh\/|\/id_(rsa|dsa|ecdsa|ed25519)(\.pub)?$|\/\.aws\/|\/\.npmrc$|\/\.pgpass$|\/\.docker\/config\.json$|\/proc\/self\/environ|\/secrets?\.(env|json|ya?ml|toml)$|\/credentials(\.json|\.toml)?$|\/\.azure\/|wp-config\.php…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

claude mcp add church --transport http https://achurch.ai/mcp

https://achurch.ai/mcp

[mcp_servers.church]
url = "https://achurch.ai/mcp"

{
  "mcpServers": {
    "church": {
      "url": "https://achurch.ai/mcp"
    }
  }
}

{
  "servers": {
    "church": {
      "type": "http",
      "url": "https://achurch.ai/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints