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

**Site creation progress.** How far a new site's creation has got, step by step, and whether its install login is ready to be revealed (once, with corestack_site_provisioning_reveal). Scope: read.

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

## When to use it

How far a new site's creation has got, step by step, and whether its install login is ready to be revealed (once, with corestack_site_provisioning_reveal).

While the site's certificate is still being issued, the `operation`'s `notes` carry `certificate_on_its_way` ("Certificate on its way: …"), as corestack_site_operation_get does. It is not a failure: the creation carries on by itself, for up to a few hours.

`create_fallbacks` is there only when the create installs something in place of a default not yet open to new sites: `{field, from, to, reason, message}` each, `to` being what is installed, and `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."). 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).

`version_wait` is there only while the create waits for a release of its line to finish testing: `{line, edition, pin, label, reason, since, message}`. Nothing is installed until a release qualifies; tell the person its `message`.

Whenever the Control Panel requests the release's security testing itself, `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)

### Input schema

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

## Refusals

- `provisioning`: the site is still being created; wait for corestack_site_provisioning_get to finish.
- 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_provisioning_get",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

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

## The same task elsewhere

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