# HaloPSA (oci · ghcr.io/wyre-technology/halopsa-mcp:v1.7.11)

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

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/wyre-technology/halopsa-mcp:v1.7.11`: 37/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-halopsa-mcp/ghcr-io-wyre-technology-halopsa-mcp-v1-7-11.md), [page](https://verifymcp.io/servers/wyre-technology-halopsa-mcp/ghcr-io-wyre-technology-halopsa-mcp-v1-7-11)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/halopsa-mcp:v1.7.11`
- 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-08-22.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **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 0 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 1148 tokens (~54/item across 21 items; 20 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 74/100
  - 95% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 32% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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 ghcr.io/wyre-technology/halopsa-mcp:v1.7.11. 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-technology-halopsa-mcp -- docker run --rm -i ghcr.io/wyre-technology/halopsa-mcp:v1.7.11
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-technology-halopsa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/halopsa-mcp:v1.7.11"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-technology-halopsa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/halopsa-mcp:v1.7.11"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-technology-halopsa-mcp -- docker run --rm -i ghcr.io/wyre-technology/halopsa-mcp:v1.7.11
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-technology-halopsa-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/halopsa-mcp:v1.7.11"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-technology-halopsa-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/halopsa-mcp:v1.7.11"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-technology-halopsa-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/halopsa-mcp:v1.7.11"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-technology-halopsa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/halopsa-mcp:v1.7.11"
      ]
    }
  }
}
```

## 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-08-21 (score 37)

First indexed and scored.

## MCP tools (20)

### `halopsa_navigate` (~139 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` (~17 tokens)

Show credentials status and available domains

### `halopsa_tickets_list` (~185 tokens)

List tickets with optional filters by client, status, agent, open/closed state, date occurred range, or full-text search

Input parameters:

- `agent_id` (number)
- `client_id` (number)
- `closed_only` (boolean)
- `dateoccurred_end` (string): ISO-8601 end date for tickets
- `dateoccurred_start` (string): ISO-8601 start date for tickets (e.g. 2026-04-06T00:00:00Z)
- `limit` (number): Maximum number of results (default: 50)
- `open_only` (boolean)
- `page_no` (number): Page number (1-indexed) for pagination
- `search` (string): Full-text search across tickets, in place of a multi-page sweep
- `status_id` (number)

### `halopsa_tickets_get` (~38 tokens)

Get ticket details by ID

Input parameters:

- `include_actions` (boolean): Include actions/notes
- `ticket_id` (number, required)

### `halopsa_tickets_create` (~70 tokens)

Create ticket

Input parameters:

- `agent_id` (number)
- `client_id` (number, required)
- `details` (string)
- `priority_id` (number)
- `site_id` (number)
- `summary` (string, required)
- `tickettype_id` (number, required)

### `halopsa_tickets_update` (~61 tokens)

Update ticket

Input parameters:

- `agent_id` (number)
- `details` (string)
- `priority_id` (number)
- `status_id` (number)
- `summary` (string)
- `ticket_id` (number, required)

### `halopsa_tickets_add_action` (~59 tokens)

Add note to ticket

Input parameters:

- `hidden_from_user` (boolean)
- `note` (string, required)
- `outcome` (string)
- `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)

## Diagnostics

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

## Score history

- 2026-08-22: 37
- 2026-08-21: 37

## Common questions

### What is the HaloPSA MCP server?

HaloPSA is an MCP server listed in the public MCP registry as io.github.wyre-technology/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-technology/halopsa-mcp:v1.7.11).

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

HaloPSA scores 37 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 20 tools: halopsa_navigate, halopsa_status, halopsa_tickets_list, halopsa_tickets_get, halopsa_tickets_create, and 15 more. Their descriptions and schemas cost roughly 1,129 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 22 August 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

- Repository: https://github.com/wyre-technology/halopsa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-halopsa-mcp/ghcr-io-wyre-technology-halopsa-mcp-v1-7-11.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-halopsa-mcp/ghcr-io-wyre-technology-halopsa-mcp-v1-7-11.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-halopsa-mcp/ghcr-io-wyre-technology-halopsa-mcp-v1-7-11