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.

INSTANT PLUG AND PLAY

InfoVetted MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Cancel Active Vetting, Check Api Connectivity, Create Contact Group, and more

Name: InfoVetted
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The InfoVetted app connector for VS Code Copilot is a standout in the Human Resources category — giving your AI agent 12 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install InfoVetted and 3,400+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "infovetted": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About InfoVetted MCP Server

Connect your InfoVetted account to any AI agent and manage background checks through natural conversation.

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.

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

The InfoVetted MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 InfoVetted tools available for VS Code Copilot

When VS Code Copilot connects to InfoVetted through Vinkius, your AI agent gets direct access to every tool listed below — spanning background-screening, identity-verification, employment-checks, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

cancel_active_vetting

Cancel a background check

check_api_connectivity

Verify InfoVetted API status

create_contact_group

g., "Engineering Team"). Create a new organization group

create_new_vetting_check

Initiate a background check

create_screening_contact

Add a new individual for screening

get_contact_details

Get details for a specific individual

get_vetting_request_status

Check status of a vetting process

list_configured_webhooks

List active webhooks

list_contact_groups

List organizational contact groups

list_screening_contacts

List individuals being screened

list_supported_check_types

). List available background check types

list_vetting_requests

List all background check requests

Connect InfoVetted to VS Code Copilot via MCP

Follow these steps to wire InfoVetted into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using InfoVetted

Ask Copilot: "Using InfoVetted, help me...". 12 tools available

Why Use VS Code Copilot with the InfoVetted MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with InfoVetted through the Model Context Protocol.

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 + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the InfoVetted MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for InfoVetted in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with InfoVetted immediately.

"Show all active vetting requests and create a new background check for a candidate."

"Check the status of Maria Silva's background check and list all screening contacts."

"Show completed vetting results and cancel the pending check for candidate #3."

Troubleshooting InfoVetted MCP Server with VS Code Copilot

Common issues when connecting InfoVetted to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

InfoVetted + VS Code Copilot FAQ

Common questions about integrating InfoVetted MCP Server with VS Code Copilot.

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.