MCP servers and secrets

Your MCP servers and the tools they offer, and the secrets Bash uses but never shows.

Send Authorization: Bearer vk_test_... on every call. Every route of MCP servers and secrets.

POST/v1/mcp-servers/{server_id}/checkConnect now and list its tools, to prove it works.

Your API key, scope setup or all. On the card: deploy. Over HTTP it is made from the contract: fill in each {…} and every value.

Request2 fields

Path

server_idstringrequiredThe MCP server's id (mcp_...).

Type: string

Body, if you send one

user_idstringYour id for a user, to fill in their ${user_secret:NAME} headers. Absent: the company's own secrets only.

Limits: 1 to 256 characters.
Example: traveller-42

Answers 2005 fields

object"mcp_check"Always mcp_check.

Type: "mcp_check"

okbooleanWhether Bash reached the server and listed its tools.

Type: boolean

toolsstring[]The tools it offers, by name; empty when it could not be reached.

Type: string[]

reason"missing_secret" | "auth_required" | "url_not_public" | "unreachable"may be absentWhy not, when ok is false: missing_secret (see missing), auth_required (it asked for credentials), url_not_public, or unreachable.

Type: "missing_secret" | "auth_required" | "url_not_public" | "unreachable"

missingstring[]may be absentWith missing_secret, the secrets to store first, by name.

Type: string[]

HTTP

No sample in your language for this route, so here it is over HTTP.

curl -X POST "$VESTRA_BASE_URL/v1/mcp-servers/{server_id}/check" \  -H "Authorization: Bearer $VESTRA_API_KEY"