# Introduction

The **Candidate MCP** server is for Checkr accounts that want to embed background check retrieval inside their own LLM agents — so a candidate can chat with the agent and pull their own report. With Candidate MCP, your agent can:

- Verify a candidate's identity via email OTP
- Retrieve the candidate's latest background check report (status, per-screening breakdown, dispute/exception info, candidate portal link)


## What the candidate sees

```text
Candidate: I'd like to check my report.
Agent:     Sure — what email address is associated with your background check?

Candidate: jane@example.com
Agent:     A 6-digit code has been sent to jane@example.com. Please enter it here.

Candidate: 392014
Agent:     Verified. Here's the latest on your report:
           - Overall status: complete
           - Result: clear
           - Screenings: SSN trace (clear), national criminal (clear), MVR (clear)
           - You can view the full report at https://candidate.checkr.com/login
```

Three MCP tools handle this end-to-end: `request_candidate_verification`, `verify_candidate_otp`, `get_report`. The full reference is in [Available Tools](/mcp/candidate/tools).

Candidate MCP is available in Production and Staging:

| Environment | Endpoint |
|  --- | --- |
| Production | `https://mcp.checkr.com/candidate-mcp/` |
| Staging | `https://mcp.checkr-staging.com/candidate-mcp/` |


Unlike the Customer MCP, the Candidate MCP uses **OAuth 2.0 Client Credentials** — your account provisions a Client ID and Client Secret in the Checkr Dashboard once, then your agent exchanges them for short-lived bearer tokens at runtime.