# Action1 (oci · ghcr.io/wyre-ai/action1-mcp)

Action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/action1-mcp`
- Version: `v1.1.9`
- 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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 458 tokens (~65/item across 7 items; 6 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Action1 MCP server?

Action1 runs locally as a container image, launched with docker run --rm -i -e ACTION1_API_KEY -e ACTION1_SECRET -e ACTION1_REGION -e ACTION1_DEFAULT_ORG_ID -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/action1-mcp:v1.1.9. 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-action1-mcp -- docker run --rm -i -e ACTION1_API_KEY -e ACTION1_SECRET -e ACTION1_REGION -e ACTION1_DEFAULT_ORG_ID -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/action1-mcp:v1.1.9
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACTION1_API_KEY",
        "-e",
        "ACTION1_SECRET",
        "-e",
        "ACTION1_REGION",
        "-e",
        "ACTION1_DEFAULT_ORG_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/action1-mcp:v1.1.9"
      ]
    }
  }
}
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACTION1_API_KEY",
        "-e",
        "ACTION1_SECRET",
        "-e",
        "ACTION1_REGION",
        "-e",
        "ACTION1_DEFAULT_ORG_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/action1-mcp:v1.1.9"
      ]
    }
  }
}
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp -- docker run --rm -i -e ACTION1_API_KEY -e ACTION1_SECRET -e ACTION1_REGION -e ACTION1_DEFAULT_ORG_ID -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/action1-mcp:v1.1.9
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "ACTION1_API_KEY",
        "-e",
        "ACTION1_SECRET",
        "-e",
        "ACTION1_REGION",
        "-e",
        "ACTION1_DEFAULT_ORG_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/action1-mcp:v1.1.9"
      ],
      "enabled": true
    }
  }
}
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "ACTION1_API_KEY", "-e", "ACTION1_SECRET", "-e", "ACTION1_REGION", "-e", "ACTION1_DEFAULT_ORG_ID", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/action1-mcp:v1.1.9"]
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACTION1_API_KEY",
        "-e",
        "ACTION1_SECRET",
        "-e",
        "ACTION1_REGION",
        "-e",
        "ACTION1_DEFAULT_ORG_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/action1-mcp:v1.1.9"
      ]
    }
  }
}
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-action1-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ACTION1_API_KEY",
        "-e",
        "ACTION1_SECRET",
        "-e",
        "ACTION1_REGION",
        "-e",
        "ACTION1_DEFAULT_ORG_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/action1-mcp:v1.1.9"
      ]
    }
  }
}
```

This image reads ACTION1_API_KEY, ACTION1_SECRET, ACTION1_REGION, ACTION1_DEFAULT_ORG_ID, 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-18 (score 44, +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-10-17 (score 43, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-15 (score 42, +33)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

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

- [functional] Package version: v1.1.8 → v1.1.9

### 2026-10-07 (score 9)

First indexed and scored.

## MCP tools (6)

### `action1_navigate` (~62 tokens)

Discover available Action1 tools by domain. All tools are callable at any time — this is a help/discovery aid.

Input parameters:

- `domain` (string, required): endpoints (device inventory), organizations (multi-tenant MSP), policies (automation visibility), updates (missing patches).

### `action1_list_organizations` (~59 tokens)

List all Action1 organizations (tenants) accessible to the configured credentials. Use this first when working with multi-tenant data — the returned org IDs are required by other tools (list_endpoints, list_policies, list_missing_updates).

### `action1_list_endpoints` (~96 tokens)

List all endpoints (managed devices) in an Action1 organization. Returns id, hostname, OS, status, last-seen, and group membership. Use the organization id from action1_list_organizations.

Input parameters:

- `limit` (number): Max results to return (default 100, max 500).
- `organization_id` (string): Action1 organization id. If omitted, uses ACTION1_DEFAULT_ORG_ID from credentials.

### `action1_get_endpoint` (~70 tokens)

Get a single endpoint by id, with full detail: hardware, installed agent version, last contact, group memberships, custom attributes.

Input parameters:

- `endpoint_id` (string, required): Action1 endpoint id (required).
- `organization_id` (string): Organization id scope. Defaults to ACTION1_DEFAULT_ORG_ID.

### `action1_list_policies` (~62 tokens)

List Action1 policies (automations, deployment rules, remediation policies) in an organization. Use org id from action1_list_organizations.

Input parameters:

- `organization_id` (string): Organization id. Defaults to ACTION1_DEFAULT_ORG_ID from credentials if omitted.

### `action1_list_missing_updates` (~92 tokens)

List missing OS / application patches across endpoints in an Action1 organization. Returns update id, severity, affected endpoint count, KB/CVE references. Use org id from action1_list_organizations.

Input parameters:

- `limit` (number): Max results to return (default 100, max 500).
- `organization_id` (string): Organization id. Defaults to ACTION1_DEFAULT_ORG_ID from credentials if omitted.

## Diagnostics

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

## Score history

- 2026-10-18: 44
- 2026-10-17: 43
- 2026-10-16: 42
- 2026-10-15: 42
- 2026-10-14: 9
- 2026-10-13: 9
- 2026-10-12: 9
- 2026-10-10: 9
- 2026-10-07: 9

## Common questions

### What is the Action1 MCP server?

Action1 is an MCP server listed in the public MCP registry as io.github.WYRE-AI/action1-mcp. Action1 MCP server, endpoint inventory, patch visibility, and policy automation via REST API. This page covers its container image (ghcr.io/wyre-ai/action1-mcp).

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

Action1 scores 44 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 Action1 MCP server expose?

Action1 exposes 6 tools: action1_navigate, action1_list_organizations, action1_list_endpoints, action1_get_endpoint, action1_list_policies, action1_list_missing_updates. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.

### Is the Action1 MCP server still maintained?

Action1 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 Action1 MCP server under?

Action1 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/action1-mcp
- Repository: https://github.com/WYRE-AI/action1-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-action1-mcp/ghcr-io-wyre-ai-action1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-action1-mcp/ghcr-io-wyre-ai-action1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-action1-mcp/ghcr-io-wyre-ai-action1-mcp