Check a custom server address
well_probe_mcp_serverCheck the address of an MCP server that a person gave for a tool Well's catalog does not carry, before anyone connects it. It sends a few read-only requests to a public https address (the MCP "initialize" request and the OAuth discovery documents), follows no redirect to a private or non-https address, and names the sign-in the server asks for. It writes nothing, signs in to nothing and sends no credential.
Call it only with an address the person gave, after a well_list_connectors read with the tool's slug (then q) found no connectable row. Read outcome:
"mcp_server": name the sign-in in words from
sign_in(no sign-in, a key to paste, or a sign-in on the tool's own page)."not_mcp_server": say the address answers but is not an MCP server, and ask once for the server's address (often a path such as /mcp or /sse).
"unreachable": say the address did not answer, and ask the person to check it.
"address_refused": say Well connects only to a public https address. Nothing was sent.
Never write the full address back in a log line or a public place.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full address of the MCP server, exactly as the person gave it, e.g. "https://mcp.example.com/mcp". Never an address you composed or guessed. | |
| workspace_id | No | Target workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | The host of the address, to name the server in your line. | |
| error | No | ||
| outcome | No | "mcp_server" (the address answers as an MCP server), "not_mcp_server" (it answers, but not as an MCP server), "unreachable" (no answer in time), or "address_refused" (not a public https address; nothing was sent). | |
| sign_in | No | Only for "mcp_server": "none" (no sign-in), "api_key" (a key or token the person pastes), "oauth" (the person signs in on the tool's own page), or "unknown" (the check did not finish). Null for every other outcome. | |
| success | Yes | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |