Monitor an authenticated MCP endpoint.
Keep connection and tool inventory evidence for a public HTTPS endpoint you are authorized to monitor.
Configure access, then test the connection
- Save the endpoint and open Endpoint access. Saving a monitor or credentials does not verify MCP.
- For an endpoint-authorized bearer token, enter New token under Bearer token, then choose Save or replace token. Credentials are encrypted in storage and are not shown again. Keep them out of endpoint URLs and tool arguments.
- For the supported OAuth pilot, choose Discover and review provider. Review the issuer, token destination, resource and scopes; enter the Preregistered client ID, acknowledge the destination, then choose Continue to provider authorization.
- Choose Test connection and inventory after configuring access. Inspect the resulting connection status and tool inventory when available.
The OAuth pilot requires MCP resource metadata, PKCE S256 and a preregistered public client or client_secret_post. Automatic registration, multiple issuers and other client authentication methods are unsupported. If the provider cannot use this flow, use an endpoint-authorized bearer token if your provider offers one, or ask your provider which supported access method it offers.
Illustrative example
Save https://mcp.example/mcp and configure its endpoint-authorized token. If the setup observation completes initialization and tools/list, you can inspect the returned inventory. The example domain is reserved; this is not a provider compatibility result.
What the observation establishes
Setup duration includes queueing, authentication and MCP connection/inventory. This explicit setup test executes no tools, sends no evidence to a model and adds no scheduled availability history. Authentication does not approve fixed tool calls or model review. Replacing or removing credentials disables saved execution and quality approvals.
Worked monitoring examples
How MCP connection monitoring works → · Understand tool checks →