Probe an MCP server
Connects to an MCP server before you save it and reports whether it answers, whether it needs a sign-in, and which tools it offers. Nothing is saved.
Scopes: tool:write
Authorizations
An API key from Settings → API keys, sent as Authorization: Bearer kb_live_…. A workspace key starts kb_; a personal key starts kbp_ and acts as its owner.
Headers
The API version to answer as, a date (YYYY-MM-DD). Leave it out for the current version (2026-11-07). An unknown version is refused with 400 unsupported_api_version.
2026-11-07 "2026-11-07"
Body
8 - 2000sse, streamable_http How the tool authenticates to its own endpoint.
token/value are write-only: a client sends plaintext here when
creating or editing a tool, and the server moves it into a sealed
tool_credential (kallabot.services.tools); the tool keeps only
{type: 'credential', credential_id}. Nothing that reads a tool back
carries the secret; the credential shows a hint (last four characters).
Response
Successful Response
True when the server answered and listed its tools.
connected, needs_auth, or an error status.
An error code when it failed.
What the server says about itself.
A fingerprint of the tool list.
{name, description, parameters, required, input_schema, annotations} for each tool.