Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

Available components

+3 this week 77 Trust /100

Last scanned (17 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 577 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://partners.cbgc.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cbgc.io CN=Amazon RSA 2048 M04,O=Amazon,C=US 27 Oct 2026 12 May 2027 RSA 2048 SHA256-RSA 2283f5cbc9f02c6bd8f2680b505d95d
SANs: cbgc.io, *.cbgc.io, *.partners.cbgc.io
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of partners.cbgc.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
cbgc.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://partners.cbgc.io/mcp Verified 200
http (plaintext) http://partners.cbgc.io/mcp HTTPS enforced 301 https://partners.cbgc.io:443/mcp
MCP tools · 7 exposed · ~456 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_error ~71

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).

NameTypeReqDescription
codestringyesThe error `code`, e.g. client_not_found.

No output schema declared.

No examples provided.

get_guide_section ~70

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

NameTypeReqDescription
headingstringyesThe section's heading or number, e.g. 'Webhooks' or '9'.

No output schema declared.

No examples provided.

get_operation ~83

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'.

NameTypeReqDescription
operationIdstringyesThe operationId (from list_operations), or 'METHOD /path'.

No output schema declared.

No examples provided.

get_webhook ~62

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.

NameTypeReqDescription
eventstringyesThe event name, e.g. check.updated.

No output schema declared.

No examples provided.

list_operations ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_webhooks ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_docs ~96

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.

NameTypeReqDescription
limitinteger–Most sections to return (default 8).
querystringyesWords to look for, e.g. 'webhook signature' or 'duplicate check'.

No output schema declared.

No examples provided.

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.

remote · partners.cbgc.io

# add to Claude Code
claude mcp add --transport http io-cbgc-partners 'https://partners.cbgc.io/mcp'
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.