---
title: "corestack_company_performance_audit_get"
url: https://docs.corefinity.com/mcp/tools/corestack_company_performance_audit_get
type: tool
last_updated: 2026-11-13
feature: performance-audits
related:
  - https://docs.corefinity.com/guides/tools/performance-audits.md
---
# corestack_company_performance_audit_get

**Read a performance audit.** Read one performance audit: its pages and environments, its last run's state, each page's mean time to first byte and status, and the run log. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Read one performance audit: its environments and pages, the state of its last run (`run.status`: queued, running, completed or failed, with `run.error` when it failed), each environment × page × cache cell's mean time to first byte (`mean_ttfb_ms`) and HTTP status, and the run log.

A cell has not run (`ran` false, `mean_ttfb_ms` null) when it has no time, or when the runner says its time is not a measurement of the page: `error` says why (for example a page that did not answer with a 2xx status, or a bot challenge), or `http_code` is 0 (no HTTP answer). Never quote a time for such a cell; say what `error` or `http_code` says instead.

Each cell also has `server_response_ms`: the time the server took to answer, which is time to first byte minus DNS, connect and TLS. Compare it with `mean_ttfb_ms` before calling a site slow: a slow connection inflates the raw time. `timing_ms` has each stage (`dns`, `tcp`, `tls`, `ttfb`, `transfer`, `total`), and `ipv4_requests` / `ipv6_requests` count the requests by address family. They are null when the cell's log does not show the connection stages.

## Inputs

- `audit_id` (integer, ≥ 1, required)

The audited sites' HTTP usernames and passwords are never answered (`http_auth` says whether one is set).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "audit_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "audit_id"
  ],
  "type": "object"
}
```

## Refusals

- `tenant_mismatch`: no such audit, or it belongs to a company you may not access.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_company_performance_audit_get",
  "arguments": {
    "audit_id": 276
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_company_performance_audit_get with audit_id 276. (Read a performance audit.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Performance audits](https://docs.corefinity.com/guides/tools/performance-audits.md)
