Vallt MCP server

Read from the package source without running it. The installed server may list more.

• vlt_connect_integration

  Start the guided integration flow for a third-party service (e.g. Stripe, Supabase, Twilio). Call without keys first to get setup instructions, then call again with the keys to validate and store them.

• vlt_disconnect_integrationwrite action

  Remove a connected integration from Vallt — deletes the keys from the OS keychain and frees up the integration slot. Use this to swap out a service or rotate a key when you've hit the free tier limit.

• vlt_get_project_context

  Fetch the full project context — build type, stack, connected integrations, recommended next. Call this at the start of a session to understand what's already set up.

• vlt_get_secret

  Check whether a secret is available in the local vallt for a given service. Never exposes the raw value — only confirms availability.

• vlt_health_check

  Check whether connected integrations are still valid. Re-validates each key against its service and surfaces degraded tokens with specific remediation steps. Runs silently in the background at session start — call this explicitly if an integration seems broken or to get a full status report.

• vlt_import_env

  Scan .env files in the current project, detect existing API keys for known services, validate them, and import them into Vallt in one shot. Use this when a user already has API keys set up and wants to bring them under Vallt management without re-entering them.

• vlt_inject_env

  Push all connected integration secrets into the project's environment — via the Vercel API, Fly.io, or as a local .env.local file.

• vlt_list_integrations

  List all connected integrations for the current project, with status and recommended next steps.

• vlt_scan_env

  Scan .env files in the current directory for security issues: secrets not gitignored, test keys in production, unfilled placeholders, and services that have keys in env files but are not yet connected to Vallt.

• vlt_validate_token

  Check auth status and subscription tier. Surfaces an upgrade prompt if the free tier is exhausted. Run this after pasting a new API token.

• Code scan37 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Vallt: common questions

Is Vallt MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Vallt safety report

How do I install Vallt?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Vallt need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Vallt maintained?

The latest release is v0.0.33.

What can I use instead of Vallt?

Servers from other publishers that do the same job: Apify MCP server, Heimdall MCP server and Polymarket Toolkit MCP server. Compare all Vallt alternatives.