HaloPSA

OCI · GHCR.IO/WYRE-TECHNOLOGY/HALOPSA-MCP:V1.7.11 · SCANNED AUG 22

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

Available components

oci · ghcr.io/wyre-technology/halopsa-mcp:v1.7.11 37

37 37 Trust /100

Trust breakdown (6 categories)

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. How we score →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
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.Unverified
Install-script risk not yet assessed.Unverified
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.Unverified

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (Apache-2.0).Pass
Actively maintained (last published 0 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability76

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 1148 tokens (~54/item across 21 items; 20 tools + 1 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage74

95% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
32% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

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.

oci · ghcr.io/wyre-technology/halopsa-mcp:v1.7.11

Claude Cursor VS Code Codex opencode Hermes Netclaw Other

# add to Claude Code

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

// .cursor/mcp.json

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

// .vscode/mcp.json

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

# add to Codex CLI

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/config.yaml

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

// ~/.netclaw/config/netclaw.json

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

// mcp.json

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

21 Aug 26 37

First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Aug 2026 · Analysed oci/ghcr.io/wyre-technology/halopsa-mcp:v1.7.11

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	oci
Reason	No attestation published

MCP tools · 20 exposed · ~1,129 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

halopsa_agents_get ~25

Get technician details by ID

Input Output Examples

Name	Type	Req	Description
agent_id	number	yes	–

No output schema declared.

No examples provided.

halopsa_agents_list ~47

List technicians

Input Output Examples

Name	Type	Req	Description
inactive	boolean	–	Include inactive
limit	number	–	Maximum number of results (default: 50)
team_id	number	–	–

No output schema declared.

No examples provided.

halopsa_assets_get ~25

Get asset details by ID

Input Output Examples

Name	Type	Req	Description
asset_id	number	yes	–

No output schema declared.

No examples provided.

halopsa_assets_list ~68

List configuration items with optional filters

Input Output Examples

Name	Type	Req	Description
assettype_id	number	–	–
client_id	number	–	–
inactive	boolean	–	Include inactive
limit	number	–	Maximum number of results (default: 50)
site_id	number	–	–

No output schema declared.

No examples provided.

halopsa_assets_list_types ~32

List asset types

Input Output Examples

Name	Type	Req	Description
limit	number	–	Maximum number of results (default: 100)

No output schema declared.

No examples provided.

halopsa_assets_search ~51

Search assets by inventory number and key fields

Input Output Examples

Name	Type	Req	Description
client_id	number	–	–
limit	number	–	Maximum number of results (default: 25)
query	string	yes	–

No output schema declared.

No examples provided.

halopsa_clients_create ~50

Create company

Input Output Examples

Name	Type	Req	Description
email	string	–	–
name	string	yes	–
notes	string	–	–
phonenumber	string	–	–
website	string	–	–

No output schema declared.

No examples provided.

halopsa_clients_get ~25

Get company details by ID

Input Output Examples

Name	Type	Req	Description
client_id	number	yes	–

No output schema declared.

No examples provided.

halopsa_clients_list ~46

List companies

Input Output Examples

Name	Type	Req	Description
inactive	boolean	–	Include inactive
limit	number	–	Maximum number of results (default: 50)
search	string	–	–

No output schema declared.

No examples provided.

halopsa_clients_search ~39

Search companies by name

Input Output Examples

Name	Type	Req	Description
limit	number	–	Maximum number of results (default: 25)
query	string	yes	–

No output schema declared.

No examples provided.

halopsa_invoices_get ~26

Get invoice details by ID

Input Output Examples

Name	Type	Req	Description
invoice_id	number	yes	–

No output schema declared.

No examples provided.

halopsa_invoices_list ~95

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

Input Output Examples

Name	Type	Req	Description
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	–	–

No output schema declared.

No examples provided.

halopsa_navigate ~139

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 Output Examples

Name	Type	Req	Description
domain	string	yes	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…

No output schema declared.

No examples provided.

halopsa_status ~17

Show credentials status and available domains

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

halopsa_teams_list ~31

List teams

Input Output Examples

Name	Type	Req	Description
limit	number	–	Maximum number of results (default: 50)

No output schema declared.

No examples provided.

halopsa_tickets_add_action ~59

Add note to ticket

Input Output Examples

Name	Type	Req	Description
hidden_from_user	boolean	–	–
note	string	yes	–
outcome	string	–	–
ticket_id	number	yes	–
timetaken	number	–	Minutes

No output schema declared.

No examples provided.

halopsa_tickets_create ~70

Create ticket

Input Output Examples

Name	Type	Req	Description
agent_id	number	–	–
client_id	number	yes	–
details	string	–	–
priority_id	number	–	–
site_id	number	–	–
summary	string	yes	–
tickettype_id	number	yes	–

No output schema declared.

No examples provided.

halopsa_tickets_get ~38

Get ticket details by ID

Input Output Examples

Name	Type	Req	Description
include_actions	boolean	–	Include actions/notes
ticket_id	number	yes	–

No output schema declared.

No examples provided.

halopsa_tickets_list ~185

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

Input Output Examples

Name	Type	Req	Description
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	–	–

No output schema declared.

No examples provided.

halopsa_tickets_update ~61

Update ticket

Input Output Examples

Name	Type	Req	Description
agent_id	number	–	–
details	string	–	–
priority_id	number	–	–
status_id	number	–	–
summary	string	–	–
ticket_id	number	yes	–

No output schema declared.

No examples provided.

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

21 Aug 22 Aug