# Alga PSA (oci · ghcr.io/wyre-ai/alga-psa-mcp)

Read-only Alga PSA MCP server: 42 curated GET tools for tickets, clients, time and billing.

- Trust score: 41/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/alga-psa-mcp`
- Version: `v1.0.0`
- 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-11-21.

- **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 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 3337 tokens (~79/item across 42 items; 42 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% 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 42 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 42 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.

**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 Alga PSA MCP server?

Alga PSA runs locally as a container image, launched with docker run --rm -i -e ALGA_INSTANCE_URL -e ALGA_API_KEY -e ALGA_TENANT_ID -e ALGA_TOOL_TIERS ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0. 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-alga-psa-mcp -- docker run --rm -i -e ALGA_INSTANCE_URL -e ALGA_API_KEY -e ALGA_TENANT_ID -e ALGA_TOOL_TIERS ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALGA_INSTANCE_URL",
        "-e",
        "ALGA_API_KEY",
        "-e",
        "ALGA_TENANT_ID",
        "-e",
        "ALGA_TOOL_TIERS",
        "ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALGA_INSTANCE_URL",
        "-e",
        "ALGA_API_KEY",
        "-e",
        "ALGA_TENANT_ID",
        "-e",
        "ALGA_TOOL_TIERS",
        "ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp -- docker run --rm -i -e ALGA_INSTANCE_URL -e ALGA_API_KEY -e ALGA_TENANT_ID -e ALGA_TOOL_TIERS ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "ALGA_INSTANCE_URL",
        "-e",
        "ALGA_API_KEY",
        "-e",
        "ALGA_TENANT_ID",
        "-e",
        "ALGA_TOOL_TIERS",
        "ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0"
      ],
      "enabled": true
    }
  }
}
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "ALGA_INSTANCE_URL", "-e", "ALGA_API_KEY", "-e", "ALGA_TENANT_ID", "-e", "ALGA_TOOL_TIERS", "ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0"]
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALGA_INSTANCE_URL",
        "-e",
        "ALGA_API_KEY",
        "-e",
        "ALGA_TENANT_ID",
        "-e",
        "ALGA_TOOL_TIERS",
        "ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-alga-psa-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALGA_INSTANCE_URL",
        "-e",
        "ALGA_API_KEY",
        "-e",
        "ALGA_TENANT_ID",
        "-e",
        "ALGA_TOOL_TIERS",
        "ghcr.io/wyre-ai/alga-psa-mcp:v1.0.0"
      ]
    }
  }
}
```

This image reads ALGA_INSTANCE_URL, ALGA_API_KEY, ALGA_TENANT_ID and ALGA_TOOL_TIERS. 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-11-21 (score 41, +1)

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

### 2026-11-18 (score 40, +1)

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

### 2026-11-16 (score 39, +1)

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

### 2026-11-14 (score 38, +1)

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

### 2026-11-12 (score 37, +1)

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

### 2026-11-10 (score 36, +1)

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

### 2026-11-09 (score 35)

First indexed and scored.

## MCP tools (42)

### `alga_tickets_list` (~278 tokens)

List tickets, one page at a time. Use to browse or filter by client, board, status, priority, assignee, open or closed, dates or external link.

Input parameters:

- `assigned_to` (string)
- `board_id` (string)
- `client_id` (string)
- `closed_from` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `closed_to` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `entered_from` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `entered_to` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `external_id` (string)
- `external_system` (string)
- `fields` (string): Comma-separated columns to return.
- `is_closed` (boolean)
- `is_open` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `priority_id` (string)
- `search` (string)
- `sort` (string)
- `status_id` (string)

### `alga_tickets_get` (~35 tokens)

Get one ticket by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_tickets_search` (~136 tokens)

Search tickets by text and return up to limit matches (not paginated). Closed tickets are left out unless include_closed is true. Narrow with comma-separated client, status, priority or assignee IDs.

Input parameters:

- `assigned_to_ids` (string): Comma-separated IDs.
- `client_ids` (string): Comma-separated IDs.
- `fields` (string): Comma-separated columns to search in.
- `include_closed` (boolean)
- `limit` (integer)
- `priority_ids` (string): Comma-separated IDs.
- `query` (string, required)
- `status_ids` (string): Comma-separated IDs.

### `alga_tickets_comments_list` (~88 tokens)

List comments on a ticket. Internal notes are included for internal users; each comment's is_internal flag says which. Use limit (up to 200) and offset to read long threads in parts.

Input parameters:

- `content_format` (string)
- `id` (string, required)
- `limit` (integer)
- `offset` (integer)
- `order` (string)

### `alga_tickets_time_entries_list` (~55 tokens)

Get the time logged on a ticket (not paginated). Users who can read every time sheet see all entries; others see their own entries plus a total for everyone else's.

Input parameters:

- `id` (string, required)

### `alga_tickets_assets_list` (~31 tokens)

List all assets linked to a ticket (not paginated).

Input parameters:

- `id` (string, required)

### `alga_tickets_get_by_external_link` (~61 tokens)

Get the ticket linked to a record in another system, using that system's name and the record's ID there.

Input parameters:

- `external_id` (string, required)
- `external_parent_id` (string)
- `system` (string, required)

### `alga_clients_list` (~85 tokens)

List clients, one page at a time. Use to browse or filter by name search, type or inactive state.

Input parameters:

- `client_type` (string)
- `is_inactive` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)

### `alga_clients_get` (~34 tokens)

Get one client by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_clients_locations_list` (~30 tokens)

List all locations belonging to a client (not paginated).

Input parameters:

- `id` (string, required)

### `alga_clients_contacts_list` (~84 tokens)

List contacts belonging to one client, one page at a time. Use alga_contacts_list to browse across clients or alga_contacts_search to find a person by name or email.

Input parameters:

- `id` (string, required)
- `is_inactive` (boolean)
- `limit` (integer)
- `page` (integer)
- `search` (string)

### `alga_contacts_list` (~96 tokens)

List contacts, one page at a time. Use to browse or filter by client or inactive state; use alga_contacts_search to find a person by name or email.

Input parameters:

- `client_id` (string)
- `is_inactive` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)

### `alga_contacts_get` (~34 tokens)

Get one contact by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_contacts_search` (~93 tokens)

Search contacts by name, email or other columns and return up to limit matches (not paginated). Optionally limit to one client or include inactive contacts.

Input parameters:

- `client_id` (string)
- `fields` (string): Comma-separated columns to match the query against (not the columns returned).
- `include_inactive` (boolean)
- `limit` (integer)
- `query` (string, required)

### `alga_time_entries_list` (~259 tokens)

List time entries, one page at a time. Use to browse or filter by user, work item, dates or billable state.

Input parameters:

- `approval_status` (string)
- `date_from` (string): Date as YYYY-MM-DD.
- `date_to` (string): Date as YYYY-MM-DD.
- `end_time_from` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `end_time_to` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `is_billable` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `service_id` (string)
- `sort` (string)
- `start_time_from` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `start_time_to` (string): UTC date-time, for example 2026-03-01T00:00:00Z.
- `user_id` (string)
- `work_item_id` (string)
- `work_item_type` (string)

### `alga_time_entries_get` (~36 tokens)

Get one time entry by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_time_sheets_list` (~87 tokens)

List time sheets, one page at a time. Use to browse or filter by user, period or approval state.

Input parameters:

- `approval_status` (string)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `period_id` (string)
- `sort` (string)
- `user_id` (string)

### `alga_projects_task_status_mappings_list` (~86 tokens)

List the task statuses a project uses, in the order Alga shows them, with the ID Alga uses for each (project_status_mapping_id). Pass phase_id to get the statuses for one phase; if that phase has no statuses of its own, you get the project's.

Input parameters:

- `phase_id` (string)
- `project_id` (string, required)

### `alga_projects_list` (~98 tokens)

List projects, one page at a time. Use to browse or filter by client, status or search.

Input parameters:

- `client_id` (string)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)
- `status` (string): A project status ID; get IDs from alga_statuses_list with type=project.

### `alga_projects_get` (~34 tokens)

Get one project by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_projects_phases_list` (~34 tokens)

List all phases in a project. This list is not paginated.

Input parameters:

- `project_id` (string, required)

### `alga_projects_tasks_list` (~61 tokens)

List all tasks in a project. Pass phase_id to list only one phase; get phase IDs from alga_projects_phases_list. These lists are not paginated.

Input parameters:

- `phase_id` (string)
- `project_id` (string, required)

### `alga_projects_tasks_get` (~37 tokens)

Get one project task by ID. Use after a list or search to see full details.

Input parameters:

- `task_id` (string, required)

### `alga_assets_list` (~103 tokens)

List assets, one page at a time. Use to browse or filter by client, type, status or location; use alga_assets_search to find assets by text.

Input parameters:

- `asset_type` (string)
- `client_id` (string)
- `limit` (integer)
- `location_id` (string)
- `order` (string)
- `page` (integer)
- `search` (string)
- `status` (string)

### `alga_assets_get` (~34 tokens)

Get one asset by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_assets_search` (~64 tokens)

Search assets by text and return up to limit matches (not paginated). To filter by client, type or status, use alga_assets_list instead.

Input parameters:

- `include_extension_data` (boolean)
- `limit` (integer)
- `query` (string, required)

### `alga_invoices_list` (~139 tokens)

List invoices, one page at a time. Filter by client, status, invoice date range or due date range (YYYY-MM-DD, inclusive).

Input parameters:

- `client_id` (string)
- `due_date_from` (string): Date as YYYY-MM-DD.
- `due_date_to` (string): Date as YYYY-MM-DD.
- `invoice_date_from` (string): Date as YYYY-MM-DD.
- `invoice_date_to` (string): Date as YYYY-MM-DD.
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `sort` (string)
- `status` (string)

### `alga_invoices_get` (~35 tokens)

Get one invoice by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_invoices_items_list` (~31 tokens)

List all line items on an invoice (not paginated).

Input parameters:

- `id` (string, required)

### `alga_users_list` (~74 tokens)

List users, one page at a time. Use to browse or filter by search or inactive state.

Input parameters:

- `is_inactive` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)

### `alga_users_get` (~35 tokens)

Get one user profile by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

### `alga_teams_list` (~92 tokens)

List teams of users, one page at a time. Use to browse or filter by team name, manager or whether a team has a manager.

Input parameters:

- `has_manager` (boolean)
- `limit` (integer)
- `manager_id` (string)
- `order` (string)
- `page` (integer)
- `sort` (string)
- `team_name` (string)

### `alga_boards_list` (~84 tokens)

List ticket boards, optionally filtered by name search, one page at a time. Inactive boards are left out unless include_inactive is true.

Input parameters:

- `include_inactive` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)

### `alga_statuses_list` (~103 tokens)

List statuses, one page at a time. Filter by type (ticket, project, project_task or interaction) or name search. Ticket statuses belong to a board, so type=ticket also needs board_id.

Input parameters:

- `board_id` (string)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)
- `type` (string)

### `alga_priorities_list` (~82 tokens)

List priorities, one page at a time. Use to browse or filter by priority name search or by what they apply to (item_type).

Input parameters:

- `item_type` (string)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)

### `alga_ticket_categories_list` (~88 tokens)

List ticket categories, one page at a time. Use to browse or filter by board, parent category or name search.

Input parameters:

- `board_id` (string)
- `limit` (integer)
- `page` (integer)
- `parent_category` (string)
- `search` (string)
- `sort_by` (string)
- `sort_order` (string)

### `alga_services_list` (~73 tokens)

List services, one page at a time. Use to browse or filter by name search or category.

Input parameters:

- `category_id` (string)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)

### `alga_contracts_list` (~111 tokens)

List client contracts, one page at a time (each has owner_client_id and owner_client_name); templates are not included. Filter by contract name, active state or whether a contract has plans. There is no per-client filter here.

Input parameters:

- `contract_name` (string)
- `has_plans` (boolean)
- `is_active` (boolean)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `sort` (string)

### `alga_search` (~85 tokens)

Search across record types at once. Use when you don't know the record type; pass the returned nextCursor as cursor to get more results.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `query` (string, required)
- `sort` (string)
- `types` (string): Comma-separated record types to search, for example ticket,asset.

### `alga_schedules_list` (~92 tokens)

List schedule entries, one page at a time. Filter by user or date range.

Input parameters:

- `end_date` (string): YYYY-MM-DD or an ISO 8601 date-time with offset.
- `limit` (integer)
- `page` (integer)
- `start_date` (string): YYYY-MM-DD or an ISO 8601 date-time with offset.
- `user_id` (string)

### `alga_kb_articles_list` (~103 tokens)

List knowledge articles, one page at a time. Use to browse or filter by search, category, type, audience or status.

Input parameters:

- `article_type` (string)
- `audience` (string)
- `category_id` (string)
- `limit` (integer)
- `order` (string)
- `page` (integer)
- `search` (string)
- `sort` (string)
- `status` (string)

### `alga_kb_articles_get` (~37 tokens)

Get one knowledge article by ID. Use after a list or search to see full details.

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 41
- 2026-11-20: 40
- 2026-11-19: 40
- 2026-11-18: 40
- 2026-11-17: 39
- 2026-11-16: 39
- 2026-11-15: 38
- 2026-11-14: 38
- 2026-11-13: 37
- 2026-11-12: 37
- 2026-11-11: 36
- 2026-11-10: 36
- 2026-11-09: 35

## Common questions

### What is the Alga PSA MCP server?

Alga PSA is an MCP server listed in the public MCP registry as io.github.WYRE-AI/alga-psa-mcp. Read-only Alga PSA MCP server: 42 curated GET tools for tickets, clients, time and billing. This page covers its container image (ghcr.io/wyre-ai/alga-psa-mcp).

### Is the Alga PSA MCP server safe to use?

Alga PSA scores 41 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 Alga PSA MCP server expose?

Alga PSA exposes 42 tools: alga_tickets_list, alga_tickets_get, alga_tickets_search, alga_tickets_comments_list, alga_tickets_time_entries_list, and 37 more. Their descriptions and schemas cost roughly 3,337 tokens of context every time the server is loaded.

### Is the Alga PSA MCP server still maintained?

Alga PSA is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Alga PSA MCP server under?

Alga PSA 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.

### What did VerifyMCP test on the Alga PSA MCP server?

VerifyMCP ran 12 checks on Alga PSA, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Alga PSA: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/alga-psa-mcp
- Repository: https://github.com/WYRE-AI/alga-psa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-alga-psa-mcp/ghcr-io-wyre-ai-alga-psa-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-alga-psa-mcp/ghcr-io-wyre-ai-alga-psa-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/wyre-ai-alga-psa-mcp/ghcr-io-wyre-ai-alga-psa-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-alga-psa-mcp/ghcr-io-wyre-ai-alga-psa-mcp
