---
title: "corestack_deployments_pipeline_check"
url: https://docs.corefinity.com/mcp/tools/corestack_deployments_pipeline_check
type: tool
last_updated: 2026-11-13
feature: deployment-pipeline
related:
  - https://docs.corefinity.com/api/reference/deployments/check-site-deployment-pipeline-lines.md
  - https://docs.corefinity.com/guides/sites/code-and-deployments/pipeline-stages.md
---
# corestack_deployments_pipeline_check

**Check pipeline lines.** Check lines for a pipeline stage before you save them: each line's verdict, badges and suggestion, and whether the build would open tunnels to the environment's services. Nothing is saved. Scope: read.

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

## When to use it

Check lines for a pipeline stage before you save them: each line's verdict, badges and suggestion, and whether the build would open tunnels to the environment's services. Nothing is saved or run.

A badge whose `severity` is `blocking` refuses the save of the stage. Every line of every stage runs in a shell of its own, so a line that is only `cd <dir>`, `export NAME=...`, `source ...`, `. ...` or `set ...` changes nothing for the next line: it carries the badge `own_shell` and the warning "Each line runs in its own shell, so this does nothing for the next line. Join them on one line, for example: cd web/app/themes/x && npm ci". The badge is `blocking` for a lone `cd` that a later line follows (`corestack_deployments_pipeline_stage_update` refuses it as `line_own_shell`), and a `warning` otherwise. Join the lines with `&&` instead. A preset hook's last line is followed by the preset's next steps: checked here with the hook's lines alone it reads as a `warning`, but the save refuses it, and `corestack_deployments_pipeline_get` marks it `blocking`.

The same action in the public REST API, with the same checks, refusals and scope: `POST /api/corestack/sites/{site}/deployments/pipeline/check` (`binding_id`).

## Inputs

- `site_id` (integer, ≥ 1, required)
- `binding_id` (integer, ≥ 1): Default: the environment's default binding.
- `stage` (string, one of `build`, `database`, `post_deploy`, required)
- `lines` (array of string, at most 200 items, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "binding_id": {
      "description": "Default: the environment's default binding.",
      "minimum": 1,
      "type": "integer"
    },
    "lines": {
      "items": {
        "type": "string"
      },
      "maxItems": 200,
      "type": "array"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    },
    "stage": {
      "enum": [
        "build",
        "database",
        "post_deploy"
      ],
      "type": "string"
    }
  },
  "required": [
    "site_id",
    "stage",
    "lines"
  ],
  "type": "object"
}
```

## Refusals

- 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_deployments_pipeline_check",
  "arguments": {
    "site_id": 4211,
    "stage": "build",
    "lines": [
      "npm ci",
      "npm run build"
    ]
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_pipeline_check with site_id 4211, stage build, lines ["npm ci","npm run build"]. (Check pipeline lines.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/deployments/pipeline/check](https://docs.corefinity.com/api/reference/deployments/check-site-deployment-pipeline-lines.md)
- Guide: [Pipeline](https://docs.corefinity.com/guides/sites/code-and-deployments/pipeline-stages.md)
