Skip to main content
Open an MCP connection and select Monitoring to review how it is being used.

Monitoring signals

Request history

Request history records method, tool, status, duration, and byte counts. It does not store request or response bodies. Use it to find blocked calls and slow operations without creating a second copy of resource data.

Investigate a failed request

  1. Check whether the response was 401 or 403.
  2. For 401, confirm the key is current and the client sends it as an HTTP header.
  3. For 403, open Permissions and check the scope and resource allowlist.
  4. If the request succeeded but was slow, compare its method and resource with the latency view.

Safe operations

Monitoring data is metadata about the connection. It is not a transcript of prompts, tool arguments, or returned records.