Vaultak MCP Server
AI agent runtime security — directly inside Claude, Cursor, and any MCP-compatible assistant.
What it does
The Vaultak MCP server gives any AI assistant three security superpowers:
| Tool | What it does |
|---|---|
vaultak_risk_score |
Score any AI agent 0–100 across 5 security dimensions |
vaultak_policy_check |
Check if an action should be ALLOWED or BLOCKED |
vaultak_get_policy_templates |
Get ready-to-use security policy templates |
Install
pip install vaultak-mcp
Or run directly:
uvx vaultak-mcp
Connect to Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"vaultak": {
"command": "uvx",
"args": ["vaultak-mcp"],
"env": {
"VAULTAK_API_KEY": "your_api_key_here"
}
}
}
}
Get your API key at app.vaultak.com.
Connect to Cursor
In Cursor Settings → MCP → Add Server:
{
"name": "vaultak",
"command": "uvx vaultak-mcp"
}
Example usage
Once connected, ask your AI assistant:
"Score the risk level of my agent that has access to the production database and can send emails"
"Should my agent be allowed to delete records from the users table?"
"Give me policy templates for protecting PII in my AI agent"
Tools reference
vaultak_risk_score
agent_description (required) What the agent does
capabilities (optional) List of tools/capabilities
api_key (optional) Vaultak API key for live scoring
Returns composite score (0–100), risk tier, per-dimension breakdown, and recommendations.
vaultak_policy_check
action (required) The action being attempted (delete, write, execute...)
resource (required) The resource being acted on (production_db, /etc/secrets...)
policies (optional) Policy list to evaluate against
api_key (optional) Fetch your live policies automatically
Returns ALLOW or BLOCK decision with matched policy and recommendation.
vaultak_get_policy_templates
scenario (required) One of: database_protection | file_system_limits |
api_rate_limiting | pii_protection |
production_safeguards | all
Returns ready-to-use policy JSON for your Vaultak dashboard.
Links
- Dashboard: app.vaultak.com
- Docs: docs.vaultak.com
- SDK:
pip install vaultak - Site: vaultak.com
Metadata
Release files for vaultak-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vaultak_mcp-1.0.0.tar.gz | 9.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vaultak_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / vaultak_mcp-1.0.0.tar.gz
| Download URL | vaultak_mcp-1.0.0.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb077f7af7ae6341a6ea1b4fc024f7c0cb63ab2c4069eed651da11a13628c22e
|
|
BLAKE2b-256 checksum How to use checksums |
69fd9966bb7c1e7e5f1a58d90224e7e2ca22ebdfec87ad102bccd11355486fd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / vaultak_mcp-1.0.0-py3-none-any.whl
| Download URL | vaultak_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
095dbefbcbf27d8f30b3c130e0ca63819a836f06cd6cd618adb5a25dbf94506b
|
|
BLAKE2b-256 checksum How to use checksums |
18240c8d2c6bdd4c6b67a4a39aee2ef6c4248b8ab42de6f75d884accd62d0b84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for vaultak-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.