HaloPSA MCP
HaloPSA ticket triage, SLA-breach pre-emption, and cross-client analytics for any MCP agent.
The current version, v0.2.14, was published to the official MCP registry on 2026-08-27. It is distributed through a declared package, filed under Analytics by this index, and declares 9 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using HaloPSA MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions found”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-09-01).
Contracts can change after screening, with no version bump. The gate pins HaloPSA MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for HaloPSA MCP](https://mcpindex.ai/server/io-github-servosity-halopsa-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-servosity-halopsa-mcp">Independent trust record for HaloPSA MCP</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-servosity-halopsa-mcp)<a href="https://mcpindex.ai/server/io-github-servosity-halopsa-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-halopsa-mcp" alt="mcpindex verdict" height="20" /></a>HALOPSA_BASE_URLFull API base URL. Leave blank: the CLI builds it from HALOPSA_TENANT and HALOPSA_DOMAIN. Set it only to point at a different host.
HALOPSA_CLIENT_IDOAuth2 client_credentials ID from Configuration → Integrations → Halo PSA API.
HALOPSA_CLIENT_SECRETOAuth2 client_credentials secret.
HALOPSA_DOMAINDomain template variable. Defaults to halopsa.com.
HALOPSA_OAUTH_SCOPESets HALOPSA_OAUTH_SCOPE for the HaloPSA MCP server. Required by the generated client for credential refresh or hand-written auth flow.
HALOPSA_SCOPEOptional. OAuth2 scope (defaults to "all"); set to a narrower scope when your API application requires it
HALOPSA_TENANTYour HaloPSA tenant identifier.
HALOPSA_TOKENOptional. Pre-issued Bearer access token. Overrides the client_credentials flow when set.
HALOPSA_TOKEN_URLToken endpoint the client-credentials exchange posts to. Leave blank: the CLI derives it from the base URL.
Creator discovery & analytics across YouTube, Instagram, TikTok (30M+) + brand/sponsor intel.
AIOProductOS: revenue, feedback, work and analytics on one customer record. 71 tools, 3 apps.
CLI and MCP server for RocketCyber Managed SOC: triage, MTTR, and posture analytics.