# HaloPSA (oci · ghcr.io/wyre-ai/halopsa-mcp)

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

- Trust score: 46/100 (low)
- Change this week: +37
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- oci · `ghcr.io/wyre-ai/halopsa-mcp`: 46/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-halopsa-mcp/ghcr-io-wyre-ai-halopsa-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-halopsa-mcp/ghcr-io-wyre-ai-halopsa-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/halopsa-mcp`
- Version: `v1.8.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1781 tokens (~77/item across 23 items; 22 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 95% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the HaloPSA MCP server?

HaloPSA runs locally as a container image, launched with docker run --rm -i -e HALOPSA_CLIENT_ID -e HALOPSA_CLIENT_SECRET -e HALOPSA_TENANT -e HALOPSA_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/halopsa-mcp:v1.8.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-halopsa-mcp -- docker run --rm -i -e HALOPSA_CLIENT_ID -e HALOPSA_CLIENT_SECRET -e HALOPSA_TENANT -e HALOPSA_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/halopsa-mcp:v1.8.2
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-halopsa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ]
    }
  }
}
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "wyre-ai-halopsa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ]
    }
  }
}
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add wyre-ai-halopsa-mcp -- docker run --rm -i -e HALOPSA_CLIENT_ID -e HALOPSA_CLIENT_SECRET -e HALOPSA_TENANT -e HALOPSA_BASE_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/halopsa-mcp:v1.8.2
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-halopsa-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ],
      "enabled": true
    }
  }
}
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  wyre-ai-halopsa-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "HALOPSA_CLIENT_ID", "-e", "HALOPSA_CLIENT_SECRET", "-e", "HALOPSA_TENANT", "-e", "HALOPSA_BASE_URL", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"]
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-halopsa-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ]
    }
  }
}
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-halopsa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "HALOPSA_CLIENT_ID",
        "-e",
        "HALOPSA_CLIENT_SECRET",
        "-e",
        "HALOPSA_TENANT",
        "-e",
        "HALOPSA_BASE_URL",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/halopsa-mcp:v1.8.2"
      ]
    }
  }
}
```

This image reads HALOPSA_CLIENT_ID, HALOPSA_CLIENT_SECRET, HALOPSA_TENANT, HALOPSA_BASE_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 46, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.47 → unverified
- [functional regression] Tool coverage: 95 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: v1.8.1 → v1.8.2

### 2026-10-16 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 45, +36)

- [security improvement] Injection markers: unverified → pass
- [functional regression] Schema quality: 60 → 75
- [functional improvement] Tool coverage: 34% → 44%
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.40
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 95
- [functional] Package version: v1.7.16 → v1.8.1

### 2026-10-13 (score 9, 0)

- [security regression] Provenance: unverified → fail
- [functional regression] Security disclosure: unverified → fail

### 2026-10-12 (score 9, 0)

- [security regression] Provenance: fail → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: v1.8.0 → v1.8.1

### 2026-10-09 (score 9, −30)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 95 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: v1.7.16 → v1.8.0

### 2026-10-02 (score 39)

First indexed and scored.

## MCP tools (22)

### `halopsa_navigate` (~160 tokens)

Discover available HaloPSA tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input parameters:

- `domain` (string, required): The domain to explore: - tickets: Ticket management - list, get, create, update tickets and manage support workflow - clients: Client/company management - list and get client information and relation…

### `halopsa_status` (~45 tokens)

Show credentials presence, whether OAuth token mint succeeds, and available domains. Reports unhealthy (isError) if credentials are missing or token mint fails — presence alone is not OK.

### `halopsa_tickets_list` (~324 tokens)

List tickets with optional filters by client, status, agent, category level 1, open/closed state, date occurred range, or full-text search. category_2, category_3, and category_4 are not list filters and are rejected. Results are one page. record_count is the total number of matching tickets, not the number of tickets in this page. page_no and page_size in the result identify that page.

Input parameters:

- `agent_id` (number)
- `category_1` (string): Filter by Halo category level 1 only. category_2–category_4 are not list filters. Use halopsa_categories_list to discover values.
- `client_id` (number)
- `closed_only` (boolean)
- `dateoccurred_end` (string): ISO-8601 end of the date-occurred window. Tickets outside the window are excluded.
- `dateoccurred_start` (string): ISO-8601 start of the date-occurred window (e.g. 2026-04-06T00:00:00Z). Tickets outside the window are excluded.
- `limit` (number): Page size (default 50). Applied on every page, including the first.
- `open_only` (boolean)
- `page_no` (number): Page number, starting at 1 (default 1). The next page continues directly after this page.
- `search` (string): Full-text search across tickets, in place of a multi-page sweep
- `status_id` (number)

### `halopsa_tickets_get` (~88 tokens)

Get ticket details by ID

Input parameters:

- `include_actions` (boolean): Include actions/notes. Each action carries is_private (true when hidden from the end user, e.g. a Private Note).
- `include_private` (boolean): With include_actions, also return private/internal notes (default true). Set false for only end-user-visible actions.
- `ticket_id` (number, required)

### `halopsa_tickets_create` (~174 tokens)

Create ticket

Input parameters:

- `agent_id` (number)
- `category_1` (string): Halo category value (level 1). Use halopsa_categories_list to discover values.
- `category_2` (string): Halo category value (level 2). Use halopsa_categories_list to discover values.
- `category_3` (string): Halo category value (level 3). Use halopsa_categories_list to discover values.
- `category_4` (string): Halo category value (level 4). Use halopsa_categories_list to discover values.
- `client_id` (number, required)
- `details` (string)
- `priority_id` (number)
- `site_id` (number)
- `summary` (string, required)
- `tickettype_id` (number, required)

### `halopsa_tickets_update` (~165 tokens)

Update ticket

Input parameters:

- `agent_id` (number)
- `category_1` (string): Halo category value (level 1). Use halopsa_categories_list to discover values.
- `category_2` (string): Halo category value (level 2). Use halopsa_categories_list to discover values.
- `category_3` (string): Halo category value (level 3). Use halopsa_categories_list to discover values.
- `category_4` (string): Halo category value (level 4). Use halopsa_categories_list to discover values.
- `details` (string)
- `priority_id` (number)
- `status_id` (number)
- `summary` (string)
- `ticket_id` (number, required)

### `halopsa_tickets_add_action` (~115 tokens)

Add note to ticket. Halo rejects actions with no outcome, so a hidden/private note defaults to outcome "Private Note" when not supplied — pass outcome explicitly for a visible note.

Input parameters:

- `hidden_from_user` (boolean)
- `note` (string, required)
- `outcome` (string): Required by Halo's API for every action; defaults to "Private Note" when hidden_from_user is true and this is omitted.
- `ticket_id` (number, required)
- `timetaken` (number): Minutes

### `halopsa_clients_list` (~46 tokens)

List companies

Input parameters:

- `inactive` (boolean): Include inactive
- `limit` (number): Maximum number of results (default: 50)
- `search` (string)

### `halopsa_clients_get` (~25 tokens)

Get company details by ID

Input parameters:

- `client_id` (number, required)

### `halopsa_clients_create` (~50 tokens)

Create company

Input parameters:

- `email` (string)
- `name` (string, required)
- `notes` (string)
- `phonenumber` (string)
- `website` (string)

### `halopsa_clients_search` (~39 tokens)

Search companies by name

Input parameters:

- `limit` (number): Maximum number of results (default: 25)
- `query` (string, required)

### `halopsa_assets_list` (~68 tokens)

List configuration items with optional filters

Input parameters:

- `assettype_id` (number)
- `client_id` (number)
- `inactive` (boolean): Include inactive
- `limit` (number): Maximum number of results (default: 50)
- `site_id` (number)

### `halopsa_assets_get` (~25 tokens)

Get asset details by ID

Input parameters:

- `asset_id` (number, required)

### `halopsa_assets_search` (~51 tokens)

Search assets by inventory number and key fields

Input parameters:

- `client_id` (number)
- `limit` (number): Maximum number of results (default: 25)
- `query` (string, required)

### `halopsa_assets_list_types` (~32 tokens)

List asset types

Input parameters:

- `limit` (number): Maximum number of results (default: 100)

### `halopsa_agents_list` (~47 tokens)

List technicians

Input parameters:

- `inactive` (boolean): Include inactive
- `limit` (number): Maximum number of results (default: 50)
- `team_id` (number)

### `halopsa_agents_get` (~25 tokens)

Get technician details by ID

Input parameters:

- `agent_id` (number, required)

### `halopsa_teams_list` (~31 tokens)

List teams

Input parameters:

- `limit` (number): Maximum number of results (default: 50)

### `halopsa_invoices_list` (~95 tokens)

List invoices with optional filters by client, status, or date range

Input parameters:

- `client_id` (number)
- `invoice_date_end` (string): YYYY-MM-DD
- `invoice_date_start` (string): YYYY-MM-DD
- `limit` (number): Maximum number of results (default: 50)
- `paid` (boolean)
- `sent` (boolean)
- `status` (string)

### `halopsa_invoices_get` (~26 tokens)

Get invoice details by ID

Input parameters:

- `invoice_id` (number, required)

### `halopsa_categories_list` (~104 tokens)

List one page of Halo ticket categories. Pass a category's name as category_1–category_4 on ticket create or update, matching the category level (1–4).

Input parameters:

- `inactive` (boolean): Include inactive categories
- `limit` (integer): Page size (default: 50)
- `page_no` (integer): Page number, starting at 1 (default: 1)
- `search` (string): Full-text search across category names

### `halopsa_categories_get` (~27 tokens)

Get a Halo ticket category by ID

Input parameters:

- `category_id` (integer, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-halopsa-mcp/ghcr-io-wyre-ai-halopsa-mcp#diagnostics

## Score history

- 2026-10-18: 46
- 2026-10-17: 46
- 2026-10-16: 46
- 2026-10-15: 45
- 2026-10-14: 45
- 2026-10-13: 9
- 2026-10-12: 9
- 2026-10-09: 9
- 2026-10-05: 39
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39

## Common questions

### What is the HaloPSA MCP server?

HaloPSA is an MCP server listed in the public MCP registry as io.github.WYRE-AI/halopsa-mcp. MCP server for HaloPSA, clients, tickets, and PSA workflows via the HaloPSA REST API. This page covers its container image (ghcr.io/wyre-ai/halopsa-mcp).

### Is the HaloPSA MCP server safe to use?

HaloPSA scores 46 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the HaloPSA MCP server expose?

HaloPSA exposes 22 tools: halopsa_navigate, halopsa_status, halopsa_tickets_list, halopsa_tickets_get, halopsa_tickets_create, and 17 more. Their descriptions and schemas cost roughly 1,762 tokens of context every time the server is loaded.

### Is the HaloPSA MCP server still maintained?

HaloPSA is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the HaloPSA MCP server under?

HaloPSA declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/halopsa-mcp
- Repository: https://github.com/WYRE-AI/halopsa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-halopsa-mcp/ghcr-io-wyre-ai-halopsa-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-halopsa-mcp/ghcr-io-wyre-ai-halopsa-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-halopsa-mcp/ghcr-io-wyre-ai-halopsa-mcp