# Christian Background Checks Partner API (remote · partners.cbgc.io)

Background check API for church software: docs, plus sandbox tools at dev.partners.cbgc.io/mcp

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `partners.cbgc.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-cbgc-partners/partners.md), [page](https://verifymcp.io/servers/io-cbgc-partners/partners)

## Channel facts

- Endpoint: `https://partners.cbgc.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 577 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Christian Background Checks Partner API MCP server?

Christian Background Checks Partner API is a hosted endpoint at https://partners.cbgc.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-cbgc-partners 'https://partners.cbgc.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-cbgc-partners": {
      "url": "https://partners.cbgc.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-cbgc-partners": {
      "type": "http",
      "url": "https://partners.cbgc.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-cbgc-partners]
url = "https://partners.cbgc.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-cbgc-partners": {
      "type": "remote",
      "url": "https://partners.cbgc.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-cbgc-partners --url 'https://partners.cbgc.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-cbgc-partners:
    url: "https://partners.cbgc.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-cbgc-partners": {
      "Transport": "http",
      "Url": "https://partners.cbgc.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-cbgc-partners -t streamable-http -u 'https://partners.cbgc.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-cbgc-partners": {
      "type": "http",
      "url": "https://partners.cbgc.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 74)

First indexed and scored.

## MCP tools (7)

### `list_operations` (~40 tokens)

List API operations

Lists every operation of the API (operationId, HTTP method, path, summary), grouped by tag. Then call get_operation for one operation's full details.

### `get_operation` (~83 tokens)

Get one API operation

Full details of one API operation: description, parameters, request body fields, every response and JSON examples (the same text as its section of /llms-full.txt). Pass its operationId from list_operations (e.g. GetCheck), or 'METHOD /path'.

Input parameters:

- `operationId` (string, required): The operationId (from list_operations), or 'METHOD /path'.

### `search_docs` (~96 tokens)

Search the docs

Searches the integration guide, error catalog, changelog, operations and webhooks. Returns the best-matching sections with a snippet and a link; read one in full with get_guide_section, get_error, get_operation or get_webhook.

Input parameters:

- `limit` (integer): Most sections to return (default 8).
- `query` (string, required): Words to look for, e.g. 'webhook signature' or 'duplicate check'.

### `get_error` (~71 tokens)

Get an error code

One error code from the error catalog: its HTTP status, what it means, what to do, and whether a retry is safe. Pass the `code` from a problem details body (e.g. client_not_found).

Input parameters:

- `code` (string, required): The error `code`, e.g. client_not_found.

### `list_webhooks` (~34 tokens)

List webhook events

Lists every webhook event we send (event name and summary). Then call get_webhook for its fields and an example payload.

### `get_webhook` (~62 tokens)

Get one webhook event

One webhook event: when it is sent, its payload fields and an example (e.g. check.updated). Signature, retry and ordering rules are in the guide's webhooks section.

Input parameters:

- `event` (string, required): The event name, e.g. check.updated.

### `get_guide_section` (~70 tokens)

Read a guide section

One section of the integration guide, by heading or number (e.g. 'Webhooks', '9', 'Testing in the sandbox'). Without a match, lists the sections.

Input parameters:

- `heading` (string, required): The section's heading or number, e.g. 'Webhooks' or '9'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-cbgc-partners/partners#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 74

## Common questions

### What is the Christian Background Checks Partner API MCP server?

Christian Background Checks Partner API is an MCP server listed in the public MCP registry as io.cbgc/partners. Background check API for church software: docs, plus sandbox tools at dev.partners.cbgc.io/mcp. This page covers its hosted endpoint (https://partners.cbgc.io/mcp).

### Is the Christian Background Checks Partner API MCP server safe to use?

Christian Background Checks Partner API scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Christian Background Checks Partner API MCP server expose?

Christian Background Checks Partner API exposes 7 tools: list_operations, get_operation, search_docs, get_error, list_webhooks, and 2 more. Their descriptions and schemas cost roughly 456 tokens of context every time the server is loaded.

### Does the Christian Background Checks Partner API MCP server require authentication?

No. We connected to Christian Background Checks Partner API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Christian Background Checks Partner API MCP server still maintained?

Christian Background Checks Partner API is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Christian Background Checks Partner API MCP server?

VerifyMCP ran 13 checks on Christian Background Checks Partner API, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://partners.cbgc.io/mcp
- Website: https://partners.cbgc.io/docs
- Changelog RSS feed: https://verifymcp.io/servers/io-cbgc-partners/partners.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-cbgc-partners/partners/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-cbgc-partners/partners.json
- HTML version of this page: https://verifymcp.io/servers/io-cbgc-partners/partners
