Bring Background Screening
to Cursor
Learn how to connect InfoVetted to Cursor 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 Cursor?
Cursor's Agent mode turns InfoVetted into an in-editor superpower. Ask Cursor to generate code using live data from InfoVetted and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
InfoVetted in Cursor
InfoVetted and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect InfoVetted to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.