Bring Background Screening
to VS Code Copilot
Learn how to connect InfoVetted to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings InfoVetted data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
InfoVetted in VS Code Copilot
InfoVetted and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect InfoVetted to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.