Datasource wholesale background check API docs. Sandbox tools: sandbox.datasourcecorp.app/mcp
Scored across 7 tools
Each tool has a distinct target: error codes, guide sections, operations, webhook events, plus two list tools and a cross-cutting search. The only mild overlap is that search_docs spans the same content as the get_* tools and get_guide_section falls back to listing sections, but the descriptions explicitly state the search-then-fetch workflow, so an agent can route correctly.
Uniform snake_case verb_noun pattern throughout: get_*/list_* plus search_docs. The list/get pairing (list_operations -> get_operation, list_webhooks -> get_webhook) reinforces the pattern and makes relationships readable.
Seven tools is well within the ideal 3-15 range and each earns its place: two discovery lists, three content getters, a search entry point, and an error lookup. No redundant or filler tools.
The surface covers the full docs lifecycle: discover (list_operations, list_webhooks, search_docs), then read in full (get_operation, get_webhook, get_guide_section, get_error). Minor gaps: the changelog is only reachable through search_docs with no dedicated getter, and there is no list_errors to enumerate the catalog before calling get_error.
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).
Inputs: code (required).
One section of the integration guide, by heading or number (e.g. 'Webhooks', '9', 'Testing in the sandbox'). Without a match, lists the sections.
Inputs: heading (required).
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'.
Inputs: operationId (required).
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.
Inputs: event (required).
Lists every operation of the API (operationId, HTTP method, path, summary), grouped by tag. Then call get_operation for one operation's full details.
Inputs: no named parameters.
Lists every webhook event we send (event name and summary). Then call get_webhook for its fields and an example payload.
Inputs: no named parameters.
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.
Inputs: query (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Background check API for church software: docs, plus sandbox tools at dev.partners.cbgc.io/mcp
The world's public data, one API. License-cleared public data sources for agents, via MCP and REST.
Real-time B2B professional profiles, company firmographics & org data MCP. OAuth or API key.
Real-time B2B professional profiles, company intelligence & jobs hosted MCP. OAuth or API key.
Add one secure layer between your agents and this server.