Read and write vulnerabilities, tests, controls, people, vendors, and documents via the Vanta API to manage compliance data.
Also known as mindstone/mcp-servers, mcp-server-vanta, @mindstone/mcp-server-vanta
- Stars
- 14
- Tools
- 25
- Downloads, 30 days
- —
- Latest version
- 0.3.1
- Last commit
- Nov 16, 2026
- License
- —
What is Vanta MCP?
Vanta reads and write vulnerabilities, tests, controls, people, vendors, and documents via the Vanta API to manage compliance data. It exposes 25 tools, such as vanta_list_vulnerabilities, vanta_get_vulnerability, vanta_list_tests.
Summary generated from the project's README
About Vanta MCP server
Managing compliance data and security evidence through an AI client is what this server enables for security and compliance teams. It provides a direct interface to the Vanta API, allowing users to read and write information across various categories including vulnerabilities, tests, controls, people, vendors, and documents. By connecting to Vanta, developers can automate the retrieval of compliance summaries or the management of vendor records directly from their coding environment.
To use this server, you must configure it with a Vanta Client ID and Client Secret obtained from the Vanta Developer Console. It runs locally via npx and requires specific OAuth scopes for reading, writing, and uploading documents. The setup supports common clients like Claude Desktop, Cursor, and VS Code. The server includes 25 specialized tools, such as vanta_list_vulnerabilities for auditing risks and vanta_upload_document for attaching evidence to existing records via public HTTPS URLs.
What you can do with it
- 1Audit security vulnerabilitiesAsk the AI to list or retrieve specific details about existing security vulnerabilities in your Vanta account.
- 2Retrieve compliance summariesRequest a high-level overview of your current compliance status and summary data.
Written from the project's README. Every use case is checked against a quote from it.
How to install Vanta MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Vanta MCP in Claude Code
$ claude mcp add --env 'VANTA_CLIENT_SECRET=<YOUR_VANTA_CLIENT_SECRET>' --env 'VANTA_CLIENT_ID=<VANTA_CLIENT_ID>' mcp-server-vanta -- npx -y @mindstone/mcp-server-vantaInstall Vanta MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server-vanta": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-vanta"
],
"env": {
"VANTA_CLIENT_SECRET": "<YOUR_VANTA_CLIENT_SECRET>",
"VANTA_CLIENT_ID": "<VANTA_CLIENT_ID>"
}
}
}
}Install Vanta MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server-vanta": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-vanta"
],
"env": {
"VANTA_CLIENT_SECRET": "<YOUR_VANTA_CLIENT_SECRET>",
"VANTA_CLIENT_ID": "<VANTA_CLIENT_ID>"
}
}
}
}Install Vanta MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server-vanta","type":"stdio","command":"npx","args":["-y","@mindstone/mcp-server-vanta"],"env":{"VANTA_CLIENT_SECRET":"<YOUR_VANTA_CLIENT_SECRET>","VANTA_CLIENT_ID":"<VANTA_CLIENT_ID>"}}'Install Vanta MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server-vanta": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-vanta"
],
"env": {
"VANTA_CLIENT_SECRET": "<YOUR_VANTA_CLIENT_SECRET>",
"VANTA_CLIENT_ID": "<VANTA_CLIENT_ID>"
}
}
}
}Install Vanta MCP in Codex
$ codex mcp add mcp-server-vanta --env 'VANTA_CLIENT_SECRET=<YOUR_VANTA_CLIENT_SECRET>' --env 'VANTA_CLIENT_ID=<VANTA_CLIENT_ID>' -- npx -y @mindstone/mcp-server-vantaInstall Vanta MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server-vanta] command = "npx" args = ["-y", "@mindstone/mcp-server-vanta"] [mcp_servers.mcp-server-vanta.env] VANTA_CLIENT_SECRET = "<YOUR_VANTA_CLIENT_SECRET>" VANTA_CLIENT_ID = "<VANTA_CLIENT_ID>"
Install Vanta MCP in Gemini CLI
$ gemini mcp add -s user -e 'VANTA_CLIENT_SECRET=<YOUR_VANTA_CLIENT_SECRET>' -e 'VANTA_CLIENT_ID=<VANTA_CLIENT_ID>' mcp-server-vanta npx -- -y @mindstone/mcp-server-vantaInstall Vanta MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server-vanta": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-vanta"
],
"env": {
"VANTA_CLIENT_SECRET": "<YOUR_VANTA_CLIENT_SECRET>",
"VANTA_CLIENT_ID": "<VANTA_CLIENT_ID>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @mindstone/mcp-server-vanta 0.3.1 in an isolated container with no network and no keys. It answered and listed 25 tools.
Vanta MCP tools 25
Read from the server with tools/listvanta_list_vulnerabilitiesRead-onlyList vulnerabilities from Vanta with optional severity, integration, and deactivation filters. WORKFLOW: - Start here to review open vulnerability posture. - Use page_size and page_cursor for pagination. RELATED TOOLS: - vanta_get_vulnerability for full details on one vulnerability. RETURNS: - JSON with ok, vulnerabilities, count, and pageInfo.
vanta_get_vulnerabilityRead-onlyGet details for one Vanta vulnerability by ID.
vanta_list_testsRead-onlyList compliance tests from Vanta with optional status and framework filters.
vanta_get_testRead-onlyGet details for one Vanta compliance test by ID.
vanta_list_controlsRead-onlyList Vanta controls with an optional framework filter.
vanta_get_controlRead-onlyGet details for one Vanta control by ID.
vanta_list_peopleRead-onlyList people tracked in Vanta with optional name/email and employment-status filters.
vanta_query_test_resultsRead-onlyList test entities/results for one Vanta test with an optional entity-status filter.
vanta_get_compliance_summaryRead-onlyGet an aggregate compliance summary from Vanta framework counters.
vanta_list_frameworksRead-onlyList available compliance frameworks in Vanta with per-framework control, document, and test counters.
vanta_get_frameworkRead-onlyGet details for one Vanta framework by ID, including requirement categories and mapped controls.
vanta_list_policiesRead-onlyList policies in Vanta with their approval/review status — e.g. which policies are out of review.
| vanta_list_vulnerabilities | List vulnerabilities from Vanta with optional severity, integration, and deactivation filters. WORKFLOW: - Start here to review open vulnerability posture. - Use page_size and page_cursor for pagination. RELATED TOOLS: - vanta_get_vulnerability for full details on one vulnerability. RETURNS: - JSON with ok, vulnerabilities, count, and pageInfo. | Read-only |
| vanta_get_vulnerability | Get details for one Vanta vulnerability by ID. | Read-only |
| vanta_list_tests | List compliance tests from Vanta with optional status and framework filters. | Read-only |
| vanta_get_test | Get details for one Vanta compliance test by ID. | Read-only |
| vanta_list_controls | List Vanta controls with an optional framework filter. | Read-only |
| vanta_get_control | Get details for one Vanta control by ID. | Read-only |
| vanta_list_people | List people tracked in Vanta with optional name/email and employment-status filters. | Read-only |
| vanta_query_test_results | List test entities/results for one Vanta test with an optional entity-status filter. | Read-only |
| vanta_get_compliance_summary | Get an aggregate compliance summary from Vanta framework counters. | Read-only |
| vanta_list_frameworks | List available compliance frameworks in Vanta with per-framework control, document, and test counters. | Read-only |
| vanta_get_framework | Get details for one Vanta framework by ID, including requirement categories and mapped controls. | Read-only |
| vanta_list_policies | List policies in Vanta with their approval/review status — e.g. which policies are out of review. | Read-only |
Show all 25 toolsShow fewer tools
vanta_get_policyRead-onlyGet details for one Vanta policy by ID, including its latest version status and approved document links.
vanta_list_integrationsRead-onlyList integrations connected to Vanta with per-connection health (disabled flag and connection error message).
vanta_list_risk_scenariosRead-onlyList risk scenarios from the Vanta risk register with optional search and include-ignored filters.
vanta_get_risk_scenarioRead-onlyGet details for one Vanta risk scenario by risk ID, including scores, treatment, and review status.
vanta_list_event_logsRead-onlyList audit event logs from the Vanta account (actor, action, targets, date) with an optional start-date filter.
vanta_list_vendorsRead-onlyList vendors tracked in Vanta with optional name and status filters.
vanta_get_vendorRead-onlyGet details for one Vanta vendor by ID.
vanta_create_vendorActionCreate a new vendor in Vanta.
vanta_update_vendorActionUpdate an existing vendor in Vanta.
vanta_attach_vendor_documentActionAttach a compliance document (SOC 2 report, DPA, pen test, questionnaire) to an existing vendor in Vanta. HOW IT WORKS: - Pass a public https:// URL. The connector downloads the file and forwards the bytes to Vanta as a multipart upload. - document_type is required; Vanta rejects the upload without it. - Vanta accepts .pdf, .docx, .jpg, .png, and .xlsx files. RELATED TOOLS: - vanta_list_vendors to find the vendor_id. RETURNS: - JSON with ok, document, file_name, content_type, and size_bytes.
vanta_deactivate_vulnerability_monitoringActionDeactivate monitoring for select vulnerabilities. Vanta will not monitor a deactivated vulnerability until it is reactivated.
vanta_reactivate_vulnerability_monitoringActionReactivate vulnerabilities and resume Vanta monitoring.
vanta_upload_documentActionAttach an evidence file to an existing Vanta document. HOW IT WORKS: - document_id must be an existing Vanta document (from the Vanta Documents page); this tool does not create documents. - Pass a public https:// URL. The connector downloads the file and forwards the bytes to Vanta as a multipart upload. - Vanta files the upload as a DRAFT: the document must be submitted for review in Vanta before auditors can see it. The response says so via submission_required. RETURNS: - JSON with ok, upload, file_name, content_type, size_bytes, and submission_required.
| vanta_get_policy | Get details for one Vanta policy by ID, including its latest version status and approved document links. | Read-only |
| vanta_list_integrations | List integrations connected to Vanta with per-connection health (disabled flag and connection error message). | Read-only |
| vanta_list_risk_scenarios | List risk scenarios from the Vanta risk register with optional search and include-ignored filters. | Read-only |
| vanta_get_risk_scenario | Get details for one Vanta risk scenario by risk ID, including scores, treatment, and review status. | Read-only |
| vanta_list_event_logs | List audit event logs from the Vanta account (actor, action, targets, date) with an optional start-date filter. | Read-only |
| vanta_list_vendors | List vendors tracked in Vanta with optional name and status filters. | Read-only |
| vanta_get_vendor | Get details for one Vanta vendor by ID. | Read-only |
| vanta_create_vendor | Create a new vendor in Vanta. | Action |
| vanta_update_vendor | Update an existing vendor in Vanta. | Action |
| vanta_attach_vendor_document | Attach a compliance document (SOC 2 report, DPA, pen test, questionnaire) to an existing vendor in Vanta. HOW IT WORKS: - Pass a public https:// URL. The connector downloads the file and forwards the bytes to Vanta as a multipart upload. - document_type is required; Vanta rejects the upload without it. - Vanta accepts .pdf, .docx, .jpg, .png, and .xlsx files. RELATED TOOLS: - vanta_list_vendors to find the vendor_id. RETURNS: - JSON with ok, document, file_name, content_type, and size_bytes. | Action |
| vanta_deactivate_vulnerability_monitoring | Deactivate monitoring for select vulnerabilities. Vanta will not monitor a deactivated vulnerability until it is reactivated. | Action |
| vanta_reactivate_vulnerability_monitoring | Reactivate vulnerabilities and resume Vanta monitoring. | Action |
| vanta_upload_document | Attach an evidence file to an existing Vanta document. HOW IT WORKS: - document_id must be an existing Vanta document (from the Vanta Documents page); this tool does not create documents. - Pass a public https:// URL. The connector downloads the file and forwards the bytes to Vanta as a multipart upload. - Vanta files the upload as a DRAFT: the document must be submitted for review in Vanta before auditors can see it. The response says so via submission_required. RETURNS: - JSON with ok, upload, file_name, content_type, size_bytes, and submission_required. | Action |
Configuration
VANTA_CLIENT_SECRETRequiredSecretVanta OAuth Client Secret
VANTA_CLIENT_IDRequiredVanta OAuth Client ID
VANTA_REGIONAccepted for compatibility; US/EU/AU tenants all use api.vanta.com
VANTA_REQUEST_TIMEOUT_MSPer-request timeout in milliseconds (default 60000)
| Name | Description | |
|---|---|---|
| VANTA_CLIENT_SECRET | Vanta OAuth Client Secret | RequiredSecret |
| VANTA_CLIENT_ID | Vanta OAuth Client ID | Required |
| VANTA_REGION | Accepted for compatibility; US/EU/AU tenants all use api.vanta.com | |
| VANTA_REQUEST_TIMEOUT_MS | Per-request timeout in milliseconds (default 60000) |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablePass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@mindstone/mcp-server-vanta
Vanta compliance MCP server — read and write vulnerabilities, tests, controls, people, vendors, documents, and compliance summaries via the Vanta API.
One-click install
After clicking the button, your host will prompt you to fill: VANTA_CLIENT_ID, VANTA_CLIENT_SECRET, VANTA_REGION, VANTA_REQUEST_TIMEOUT_MS.
{
"mcpServers": {
"Vanta": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-vanta"
],
"env": {
"VANTA_CLIENT_ID": "",
"VANTA_CLIENT_SECRET": "",
"VANTA_REGION": "us",
"VANTA_REQUEST_TIMEOUT_MS": "60000"
}
}
}
}
Status
- Version: 0.3.1 · npm
- Auth: OAuth client-credentials grant (
VANTA_CLIENT_ID+VANTA_CLIENT_SECRET) - Tools: 25 (19 read + 6 write across vulnerabilities, tests, controls, frameworks, policies, integrations, risk scenarios, event logs, people, vendors, documents, compliance summary)
- Surface: cloud-api
- Regions:
VANTA_REGIONis accepted for backward compatibility; all standard tenants (US, EU, AU) share one API host (api.vanta.com). The knob routes nothing in this package.
Installation
npx -y @mindstone/mcp-server-vanta
Configuration
Set these environment variables before starting the server:
VANTA_CLIENT_ID— Vanta OAuth Client ID (required)VANTA_CLIENT_SECRET— Vanta OAuth Client Secret (required)VANTA_REGION— accepted for backward compatibility; all standard tenants (US, EU, AU) share one API host (api.vanta.com). The knob routes nothing in this package.VANTA_REQUEST_TIMEOUT_MS— request timeout in milliseconds (default 60000)
To generate credentials, open the Vanta Developer Console, create a new "Manage Vanta" app type, and copy the Client ID and Client Secret.
Requested OAuth scopes
The connector requests exactly this scope string at every token exchange:
vanta-api.all:read vanta-api.all:write vanta-api.documents:upload
vanta-api.documents:upload is a separate scope from vanta-api.all:write and is required by Vanta's document-upload endpoint. Vanta issues one active token per application and validates scopes against the application, so there is no way to request a narrower set per tool — the trade-off is accepted deliberately: every install carries the upload scope, including installs that never upload.
Upgrading from an earlier version: if your Manage Vanta app cannot request vanta-api.documents:upload, token exchange fails with invalid_scope and every tool stops working. Update (or recreate) the app in the Developer Console so it may request all three scopes.
Tools
Read
vanta_list_vulnerabilities/vanta_get_vulnerabilityvanta_list_tests/vanta_get_testvanta_list_controls/vanta_get_controlvanta_list_frameworks/vanta_get_frameworkvanta_list_policies/vanta_get_policyvanta_list_integrationsvanta_list_risk_scenarios/vanta_get_risk_scenariovanta_list_event_logsvanta_list_peoplevanta_query_test_resultsvanta_get_compliance_summaryvanta_list_vendors/vanta_get_vendor
Write
vanta_create_vendorvanta_update_vendorvanta_attach_vendor_documentvanta_deactivate_vulnerability_monitoringvanta_reactivate_vulnerability_monitoringvanta_upload_document
File uploads
Vanta's upload endpoints take the file as multipart/form-data, so both upload tools take a public https:// URL and the connector downloads the file itself before forwarding the bytes to Vanta:
vanta_upload_documentattaches evidence to an existing Vanta document (document_id), viaPOST /v1/documents/{documentId}/uploads.vanta_attach_vendor_documentattaches a document to a vendor (vendor_id, plus a requireddocument_typesuch asSOC2_REPORT), viaPOST /v1/vendors/{vendorId}/documents.
Vanta accepts .pdf, .docx, .jpg, .png, and .xlsx files.
Known limitations
- Uploads land as drafts. Vanta files an API upload against a document as a draft; the document must be submitted for review in Vanta before auditors can see the evidence. The tool result says so via
submission_required, but the connector has no tool that submits. - No document creation.
vanta_upload_documentattaches a file to a document that already exists in Vanta; it cannot create the document. - Bounded ID fallback scan. When a direct
GETby ID returns 404, the connector cursor-paginates the collection looking for the ID, up to 50 pages (5,000 records). Beyond that bound it reports not-found with a partial-scan note instead of silently giving up at the first page.
Safety
This server enforces:
- Every string in a Vanta API response is wrapped in an
<untrusted-content>envelope — with close-tag breakout escaping — before it reaches the model, unless it is a grammar-checked structural literal (identifiers, enum-like statuses, ISO-8601 dates, http(s) URLs, pagination cursors) that must stay verbatim so it can be quoted back into follow-up tool calls. This deny-by-default walk means fields Vanta adds later, and attacker-influenced fields the connector does not know (e.g. scanner-authored package identifiers), fail closed — enveloped — rather than reaching the model raw. External message text in API and OAuth error bodies is enveloped the same way; credential-shaped values are redacted. - HTTPS-only URL validation on both upload tools (rejects
file:,localhost, RFC1918, link-local incl. cloud metadata addresses, IPv6 loopback/ULA, and hostnames whose DNS records resolve to any of those). - Bounded document fetching: at most 3 redirects, each hop re-validated through the same URL guard, a 30-second timeout, and a 25 MB size cap enforced while streaming (a source cannot lie its way past the cap with a false
Content-Length). - Content-Type handling is header sanitization, not byte-level MIME sniffing: untrustworthy source labels are replaced with
application/octet-stream. - Distinct, structured failures for every refusal — blocked host, non-HTTPS, oversize, timeout, redirect limit — rather than a generic error.
- 50-requests-per-minute rate limiting with single-flight token exchange.
- Zod validation of external responses at the client boundary (paginated list envelopes and the OAuth token response); a malformed payload fails with a structured
RESPONSE_INVALID/AUTHerror instead of an unchecked cast. - Response truncation at 25 KB with binary-search trimming; a truncated response drops
pageInfoand directs a smaller-page_sizeretry, because the full-page cursor would silently skip the dropped records. - Bearer-token redaction in all error messages.
License
Vanta MCP questions
How do I add Vanta MCP to Claude Code?
Run claude mcp add --env 'VANTA_CLIENT_SECRET=<YOUR_VANTA_CLIENT_SECRET>' --env 'VANTA_CLIENT_ID=<VANTA_CLIENT_ID>' mcp-server-vanta -- npx -y @mindstone/mcp-server-vanta in your terminal. Add --scope user to make it available in every project.
How do I add Vanta MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Vanta MCP provide?
It exposes 25 tools, including vanta_list_vulnerabilities, vanta_get_vulnerability, vanta_list_tests, vanta_get_test, vanta_list_controls.
What file types can I upload to Vanta?
Vanta accepts .pdf, .docx, .jpg, .png, and .xlsx files.
Can the server create new documents in Vanta?
No, the upload tool attaches files to documents that already exist in Vanta but cannot create new ones.
Do uploaded files become immediately visible to auditors?
No, uploaded files land as drafts and must be submitted for review in Vanta before auditors can see them.