Bring Background Screening
to Claude Code
Learn how to connect InfoVetted to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the InfoVetted MCP Server?
Connect your InfoVetted account to any AI agent and manage background checks through natural conversation.
What you can do
- Vetting Requests — List all vetting requests, create new background checks, check status, and cancel active vettings
- Screening Contacts — Manage contacts for screening with full profile data, create new screening contacts, and inspect individual records
- Package Management — Browse available vetting packages and their included checks
- Result Tracking — Monitor check results with pass/fail status and compliance details
- Activity History — View submission and completion timelines
How it works
1. Subscribe to this server
2. Enter your InfoVetted API Key
3. Start managing background checks from Claude, Cursor, or any MCP-compatible client
Who is this for?
- HR Teams — initiate background checks on candidates and track results
- Compliance Officers — monitor vetting status and ensure regulatory compliance
- Staffing Agencies — manage high-volume screening workflows through AI
Built-in capabilities (12)
Cancel a background check
Verify InfoVetted API status
g., "Engineering Team"). Create a new organization group
Initiate a background check
Add a new individual for screening
Get details for a specific individual
Check status of a vetting process
List active webhooks
List organizational contact groups
List individuals being screened
). List available background check types
List all background check requests
Why Claude Code?
Claude Code registers InfoVetted as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where InfoVetted data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using InfoVetted tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
InfoVetted in Claude Code
InfoVetted and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect InfoVetted to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for InfoVetted in Claude Code
The InfoVetted MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
InfoVetted for Claude Code
Every tool call from Claude Code to the InfoVetted MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I initiate a background check through the AI agent?
Yes. Use create_new_vetting_check with the contact ID and vetting package to initiate a background check. Use create_screening_contact first if the person isn't in your system. Track progress with get_vetting_request_status.
Can I track the status of active vetting requests?
Yes. Use list_vetting_requests to see all requests with their current status. Use get_vetting_request_status for detailed progress on a specific check. Use cancel_active_vetting to stop a check that's no longer needed.
Can I manage screening contacts and their data?
Yes. Use list_screening_contacts to browse all contacts, get_screening_contact for individual profiles, and create_screening_contact to add new people to the system. Each contact can have multiple vetting requests associated.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
