checkr.com
Checkr provides background screening and related hiring workflow services. Its products include APIs, embeddable application components, and MCP servers for customers and candidate-facing AI agents.
Checkr exposes a REST API, a web-embeds SDK backed by that API, and two MCP servers (Customer MCP and Candidate MCP); auth uses API keys, partner OAuth app credentials/tokens, or Candidate MCP client-credentials depending on the surface.
- Checkr Customer MCPdetected
- Checkr Candidate MCPdiscovered
- Checkr REST APIdiscovered
- Checkr Embeds Web SDKdiscovered
In the Checkr Dashboard, go to the API key section from the getting-started flow described in the API documentation and generate/copy your account's API key. Use the staging dashboard/account for testing and the production dashboard/account for live use, as noted in the partner docs.
Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
Provision OAuth Client Credentials for Candidate MCP in the Checkr Dashboard, as described in the MCP documentation. The docs state these credentials are provisioned once in the Dashboard per Checkr account and are then used to obtain a bearer token for Candidate MCP.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing