---
title: "corestack_company_magento_keys_check"
url: https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_check
type: tool
last_updated: 2026-11-13
feature: magento
related:
  - https://docs.corefinity.com/api/reference/organisation/check-company-magento-keys.md
  - https://docs.corefinity.com/guides/platforms/magento-2.md
---
# corestack_company_magento_keys_check

**Check the Magento repository keys.** Ask repo.magento.com again whether your company's own Magento repository keys still work and include Adobe Commerce. At most 6 checks an hour per company. For a client company your agency manages, send client_company_id. Scope: write.

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

## When to use it

Ask repo.magento.com again whether your company's own Magento repository keys still work and whether they include Adobe Commerce, for example after the company's Adobe licence changed. The answer is the keys as `corestack_company_magento_keys_get` reads them, with `entitlements`. Never a key. For a client company your agency manages, send `client_company_id`.

## Inputs

- `client_company_id` (integer, at least 1): A client company your agency manages, by id. Omit for your own company.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "description": "A client company your agency manages, by id. Omit for your own company.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "type": "object"
}
```

## Refusals

- `not_configured`: your company has no keys of its own (it uses Corefinity's, or none).
- `upstream_unavailable`: repo.magento.com did not answer; the last answer stands.
- `rate_limited`: at most 6 checks an hour per company, shared with the Control Panel.
- `pin_refused`: a token limited to some sites cannot change company-wide settings.
- `tenant_mismatch` (with `client_company_id`): the company is not one your agency manages, or it does not exist; the same answer for both. Being attached to your agency is not enough: one of its live CoreStack sites must name your agency as its managing agency.
- `pin_refused` (with `client_company_id`): a token limited to some sites cannot act on a client company's keys.
- 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_company_magento_keys_check",
  "arguments": {}
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_company_magento_keys_check. (Check the Magento repository keys.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/companies/{company}/magento-keys/check](https://docs.corefinity.com/api/reference/organisation/check-company-magento-keys.md)
- Guide: [Magento 2](https://docs.corefinity.com/guides/platforms/magento-2.md)
