---
title: "corestack_error_pages_test"
url: https://docs.corefinity.com/mcp/tools/corestack_error_pages_test
type: tool
last_updated: 2026-11-13
feature: error-pages
related:
  - https://docs.corefinity.com/api/reference/site-settings/test-site-error-pages.md
  - https://docs.corefinity.com/guides/sites/site-settings/error-and-maintenance-pages.md
---
# corestack_error_pages_test

**Test an environment's error pages on the site.** Checks the site, read-only: live, what it answers for a path and who drew it; render, which pages it serves. Scope: read.

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

## When to use it

Check the site itself, read-only. Nothing is changed.

- `kind: live` asks the site for `path` (default `/`) the way a visitor would, through Cloudflare, and answers the status, the headers that matter (`server`, `cf-cache-status`, `content-type`, `retry-after`, `cache-control`), the size of the body, its first 2 KiB, and `who` drew the answer: `app`, `platform` (our page), `custom` (your page), `cloudflare` or `unknown`. Only the environment's own addresses are asked; a host that points anywhere else is refused.
- `kind: render` asks the environment for each of its pages and answers, per page, which version is live and whether it rendered. Use it after a change to see that the new pages arrived. While maintenance is on, every request gets the maintenance page, so only that page is checked.

6 tests a minute for each environment, whoever sends them.

## Inputs

- `site_id` (integer, ≥ 1, required): the environment row.
- `kind` (string, required): `live` or `render`.
- `path` (string, at most 512 characters): for `live`, the path to ask for. Starts with `/`; no `#`.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "kind": {
      "description": "live or render.",
      "enum": [
        "live",
        "render"
      ],
      "type": "string"
    },
    "path": {
      "description": "For live; default /.",
      "maxLength": 512,
      "type": "string"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "kind"
  ],
  "type": "object"
}
```

## Refusals

- `feature_off`: error pages are not available to you yet.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done.
- 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_error_pages_test",
  "arguments": {
    "site_id": 4211,
    "kind": "live",
    "path": "/checkout"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_error_pages_test with site_id 4211, kind live, path /checkout. (Test an environment's error pages on the site.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/error-pages/test](https://docs.corefinity.com/api/reference/site-settings/test-site-error-pages.md)
- Guide: [Error pages](https://docs.corefinity.com/guides/sites/site-settings/error-and-maintenance-pages.md)
