---
title: "corestack_site_get"
url: https://docs.corefinity.com/mcp/tools/corestack_site_get
type: tool
last_updated: 2026-11-13
feature: sites
related:
  - https://docs.corefinity.com/api/reference/sites/get-site.md
  - https://docs.corefinity.com/guides/sites/create-and-manage/site-overview.md
---
# corestack_site_get

**Site.** One site or environment row: its platform, versions, tier, limits, usage, health, addresses, maintenance state and the work running on it. Scope: read.

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

## When to use it

One site or environment row: its platform, versions, tier, limits, usage, health, addresses, maintenance state and the work running on it.

`site.create_fallbacks` is there only when the site's create installed something in place of a default not yet open to new sites (an older tested release or line, a newer open PHP or MariaDB version): `{field, from, to, reason, message}` each, `to` being what was installed. `message` says it in the past tense, as of the create ("PHP 8.3 was not available for new sites when this site was created, so it was set up with PHP 8.4."), so it stays true after the owner changes a version: what the site runs now is `site.runtime.php.version`, `site.runtime.mariadb.version` and `site.app_version`. A `php_version` entry also carries `now_available`, worked out on every read and never stored: true once the PHP version the create could not install (`from`) is open to new sites and the site does not run it yet, and its `message` then reads "PHP 8.3 is now available. You can switch this site to it in its PHP settings." (8.3 being `from`). The site is never moved for it: switching is the owner's choice (corestack_php_version_change). `site.app_version.created_for` names the release the site was created with.

`site.version_wait` is there only while the site's create waits for a release of its line to finish testing (`{line, edition, pin, label, reason, since, message}`): nothing is installed yet, and `site.app_version` records no version until a release qualifies and the create goes on.

Whenever the Control Panel requests the release's security testing itself, `site.version_wait` also has `testing` (`{state, since}`) and `overdue`, and `message` always reads the same state. `testing.state` is `requested` (the testing is asked for and has not started), `running` (the release is being tested), `awaiting_staff` (our team runs this release's security testing) or `team_review` (our team confirms the version: the testing has ended, the wait is for another `reason`, or it passed its bound; when the testing passed, the create goes on by itself shortly); `testing.since` is when that state began. `overdue` turns `true` once the create has waited longer than the bound our team sets: `testing.state` then reads `team_review`, and the create keeps waiting, is never failed by the bound and still goes on as soon as a release qualifies.

`version_wait` also answers a create waiting for its PHP version (none of its list was open to new sites): it then starts with `kind` `php` and `php` (the version it waits for), its `reason` is `runtime_not_open` (`runtime_not_offered` or `node_not_adopted` while our team must act), and `line`, `pin` and `label` are null for a site without an application version line. It goes on by itself once that version is open; tell the person its `message`.

## Inputs

- `site_id` (integer, ≥ 1, required): A site's id or one of its environments' ids.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "description": "A site's id or one of its environments' ids.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id"
  ],
  "type": "object"
}
```

## Refusals

- `pin_refused`: the environment shown for this site is outside the token's pins. This is checked before reading live status or changing settings, including for existing tokens when a site becomes staging-only. Add the site using the returned link, or address a covered environment by its own `site_id`. The refusal names only the requested row. A successful reply describes the environment admitted at the start of that call, even if the display environment changes while work runs; the next call checks the current display environment again.

- 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_site_get",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_site_get with site_id 4211. (Site.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}](https://docs.corefinity.com/api/reference/sites/get-site.md)
- Guide: [Site overview](https://docs.corefinity.com/guides/sites/create-and-manage/site-overview.md)
