Christian Background Checks Partner API

io.cbgcPublished by cbgc.ioOfficial publisherv1.0.0Updated Nov 14, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Read-only documentation server for the Christian Background Checks Partner API, letting an assistant look up operations, errors, webhooks and guide sections.

What you can do
  • Browse the API surface: list every operation by tag and read one operation's parameters, request and response fields and JSON examples
  • Search the docs: query the integration guide, error catalog, changelog, operations and webhooks and get matching snippets with links
  • Explain errors: look up an error code's HTTP status, meaning, remedy and whether retrying is safe
  • Inspect webhooks: list outgoing events and read one event's trigger, payload fields and example
  • Read the guide: fetch a single integration guide section by heading or number
When to use it
Useful when integrating church or ministry software with the Datasource background check API and you want an assistant to answer questions about endpoints, error codes, webhook payloads or setup steps without leaving the editor. It is a reference aid, not a way to run checks.
Requirements
Remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The production endpoint is documentation only; trying real requests requires connecting to the separate sandbox endpoint with a pk_test_ key.
Before you install
The production server is docs only and cannot place or read actual background checks. The sandbox endpoint requires an API key, so treat that key as a secret. Background check data is sensitive personal information; do not paste real applicant data into documentation lookups.

Installation

In SourceWeft

  1. Open Christian Background Checks Partner API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.cbgc%2Fpartners/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "christian-background-checks-partner-api": {
      "type": "http",
      "url": "https://partners.cbgc.io/mcp"
    }
  }
}

Tools

7

list_operations

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.

Takes no parameters.

get_operation

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

ParametersoperationIdrequired

search_docs

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.

Parameterslimitqueryrequired

get_error

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

Parameterscoderequired

list_webhooks

List webhook events

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

Takes no parameters.

get_webhook

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.

Parameterseventrequired

get_guide_section

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.

Parametersheadingrequired

Version history

1
  1. v1.0.0LatestNov 14, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.