---
title: "corestack_environment_registry_secret_list"
url: https://docs.corefinity.com/mcp/tools/corestack_environment_registry_secret_list
type: tool
last_updated: 2026-11-13
feature: registry-secrets
related:
  - https://docs.corefinity.com/guides/sites/code-and-deployments/registry-secrets.md
---
# corestack_environment_registry_secret_list

**CoreStack Enterprise registry credentials.** A CoreStack Enterprise environment's Composer registry credentials for its builds: label, host, auth type, last four characters, when each was verified and last used. Never the secret or the username. Scope: read.

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

## When to use it

List the Composer registry credentials a CoreStack Enterprise environment's builds install private packages with, as
its environment page's "Composer registries" card shows them: each credential's `id`, `label`, `registry` (the host),
`auth_type`, the last four characters of its secret (`last4`), and when it was last verified and last used by a build.
The secret and the username are never answered. Use an `id` as `secret_id` in
`corestack_environment_registry_secret_set` or `corestack_environment_registry_secret_delete`.

Saved credentials are used by the environment's builds on build pipeline version 2, and only once Composer registry
credentials are switched on for that environment; until then they are kept, and builds do not receive them. They are
given to a build for that build only and removed after it.

This is for CoreStack Enterprise environments only. A CoreStack or CoreCluster site keeps its registry secrets in
`corestack_deployments_secrets_list`, by `site_id`.

The public API's `GET /api/corestack/environments/{environment}/deploy-secrets` answers the same.

## Inputs

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

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for a CoreStack or CoreCluster site use corestack_deployments_secrets_list by site_id.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "enterprise_env_id"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` (field `enterprise_env_id`): a CoreStack or CoreCluster environment; use
  `corestack_deployments_secrets_list` by `site_id`.
- `tenant_mismatch` (the same for an environment that does not exist and one you cannot see), `pin_refused` (a token
  limited to some sites cannot reach a CoreStack Enterprise environment), and the refusals every tool can answer:
  `scope_required`, `rate_limited`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_environment_registry_secret_list",
  "arguments": {
    "enterprise_env_id": 1530
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_environment_registry_secret_list with enterprise_env_id 1530. (CoreStack Enterprise registry credentials.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Private registries](https://docs.corefinity.com/guides/sites/code-and-deployments/registry-secrets.md)
