Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Developer Platform 20 Oct 2026
One change · api

Validate an MCP OAuth Credential changedapi/beta/vaults/credentials/mcp_oauth_validate

Nearest release: v2.1.304, published 6 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+7added
Lines−7removed
From line 1 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits19to this page, all time

# Validate an MCP OAuth Credential # Validate Credential

The whole hunk

from line 1, old and new numbered
/
lines
from line 1
11---
2title: Validate Credential
2title: Validate an MCP OAuth Credential
33url: https://platform.claude.com/docs/en/api/beta/vaults/credentials/mcp_oauth_validate
44---
55 
6# Validate Credential
6# Validate an MCP OAuth Credential
77 
88**POST** `/v1/vaults/{vault_id}/credentials/{credential_id}/mcp_oauth_validate`
99 
10Validate Credential
10Validate an MCP OAuth Credential
1111 
1212## Path parameters
1313 
from line 159
159159 
160160 - `mcp_probe: BetaManagedAgentsMCPProbe or null`
161161 
162 Details of the failing MCP probe step. Null when the probe succeeded.
162 Details of the MCP probe step that failed, or `null` if the probe succeeded or there was no access token to test.
163163 
164164 - `http_response: BetaManagedAgentsRefreshHTTPResponse or null`
165165 
166 The captured HTTP error response. Null when no HTTP response was received (timeout, DNS, TLS).
166 The HTTP error response from the MCP server, or `null` if the MCP server didn't return one for the failing step, for example after a timeout or a DNS or TLS failure.
167167 
168168 - `body: string`
169169 
from line 225
225225 
226226 - `"invalid"`
227227 
228 The probe reached the MCP server and was rejected, and a refresh (if attempted) did not recover it.
228 The probe reached the MCP server and the server rejected the credential, or no access token is stored. A refresh, if one was tried, didn't recover it. Usually the end user needs to authorize again.
229229 
230230 - `"unknown"`
231231 
232 The probe could not determine validity — for example, a transport error or a successful refresh that was not re-probed.
232 The probe couldn't tell whether the credential works, for example because of a network error or because a refresh succeeded but the new access token wasn't tested. Validate the credential again to find out.
233233 
234234 - `validated_at: string`
235235 
Feedback