# Alloy Navigator (oci · ghcr.io/wyre-ai/alloy-navigator-mcp)

MCP server for Alloy Navigator's REST API - IT asset management and ITSM data for MSPs.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/alloy-navigator-mcp`
- Version: `v1.0.1`
- 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**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 799 tokens (~199/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Alloy Navigator MCP server?

Alloy Navigator runs locally as a container image, launched with docker run --rm -i -e ALLOY_BASE_URL -e ALLOY_CLIENT_ID -e ALLOY_CLIENT_SECRET -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1. 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-alloy-navigator-mcp -- docker run --rm -i -e ALLOY_BASE_URL -e ALLOY_CLIENT_ID -e ALLOY_CLIENT_SECRET -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALLOY_BASE_URL",
        "-e",
        "ALLOY_CLIENT_ID",
        "-e",
        "ALLOY_CLIENT_SECRET",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALLOY_BASE_URL",
        "-e",
        "ALLOY_CLIENT_ID",
        "-e",
        "ALLOY_CLIENT_SECRET",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp -- docker run --rm -i -e ALLOY_BASE_URL -e ALLOY_CLIENT_ID -e ALLOY_CLIENT_SECRET -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "ALLOY_BASE_URL",
        "-e",
        "ALLOY_CLIENT_ID",
        "-e",
        "ALLOY_CLIENT_SECRET",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "ALLOY_BASE_URL", "-e", "ALLOY_CLIENT_ID", "-e", "ALLOY_CLIENT_SECRET", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"]
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALLOY_BASE_URL",
        "-e",
        "ALLOY_CLIENT_ID",
        "-e",
        "ALLOY_CLIENT_SECRET",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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-alloy-navigator-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ALLOY_BASE_URL",
        "-e",
        "ALLOY_CLIENT_ID",
        "-e",
        "ALLOY_CLIENT_SECRET",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/alloy-navigator-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads ALLOY_BASE_URL, ALLOY_CLIENT_ID, ALLOY_CLIENT_SECRET, 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 38, +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-10-17 (score 37)

First indexed and scored.

## MCP tools (4)

### `alloy_list_objects` (~310 tokens)

List objects of a given Alloy Navigator object class (e.g. Incidents, Work Orders, Computers, Consumables, SoftwareCatalog, or 'Purchase Order Items' - Alloy Navigator does not publish one exhaustive class list; use the object class names configured in your instance, which typically match the module names shown in the Alloy Navigator client). Supports field selection, sorting, paging, free-text search, and per-field filters. Each returned object's OID chains into alloy_get_object and alloy_get_object_activities.

Input parameters:

- `filters` (object): Optional field-name/value pairs to filter the result, e.g. {"Priority": "High"}. Each pair is sent as a literal <fieldName>=<value> query parameter, matching Alloy Navigator's own filtering conventio…
- `objectClass` (string, required): The Alloy Navigator object class to list, e.g. 'Incidents' or 'Computers'.
- `par_fields` (string): Comma-separated list of field names to include in the result. Omit to return every field.
- `par_limit` (number): Maximum number of records to return.
- `par_offset` (number): Number of records to skip, for paging.
- `par_search_text` (string): Free-text search string to narrow the returned objects.
- `par_sort_asc` (string): Comma-separated list of field names to sort the result by, ascending.
- `par_sort_desc` (string): Comma-separated list of field names to sort the result by, descending.

### `alloy_get_object` (~57 tokens)

Get every field of a single Alloy Navigator object by its OID (e.g. a ticket number like T000002) or database record GUID.

Input parameters:

- `oid` (string, required): The object's OID or GUID (from alloy_list_objects).

### `alloy_get_object_activities` (~167 tokens)

Get the activity/history log entries recorded against a single Alloy Navigator object by its OID - e.g. status changes, assignment changes, and system-generated notes.

Input parameters:

- `oid` (string, required): The object's OID (from alloy_list_objects or alloy_get_object).
- `par_fields` (string): Comma-separated list of field names to include in the result. Omit to return every field.
- `par_limit` (number): Maximum number of records to return.
- `par_offset` (number): Number of records to skip, for paging.
- `par_sort_asc` (string): Comma-separated list of field names to sort the result by, ascending.
- `par_sort_desc` (string): Comma-separated list of field names to sort the result by, descending.

### `alloy_get_dictionary` (~265 tokens)

Get the allowed reference/classification values for a field on an Alloy Navigator object class - e.g. the valid Status or Types values for Incidents or Computers. Useful for resolving what a status/type code means, or for building a valid filter value for alloy_list_objects.

Input parameters:

- `filters` (object): Optional field-name/value pairs to filter the result, e.g. {"Priority": "High"}. Each pair is sent as a literal <fieldName>=<value> query parameter, matching Alloy Navigator's own filtering conventio…
- `objectClass` (string, required): The Alloy Navigator object class the reference field belongs to, e.g. 'Computers'.
- `par_fields` (string): Comma-separated list of field names to include in the result. Omit to return every field.
- `par_limit` (number): Maximum number of records to return.
- `par_offset` (number): Number of records to skip, for paging.
- `par_sort_asc` (string): Comma-separated list of field names to sort the result by, ascending.
- `par_sort_desc` (string): Comma-separated list of field names to sort the result by, descending.
- `refField` (string, required): The reference field name, e.g. 'Status' or 'Types'.

## Diagnostics

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

## Score history

- 2026-10-18: 38
- 2026-10-17: 37

## Common questions

### What is the Alloy Navigator MCP server?

Alloy Navigator is an MCP server listed in the public MCP registry as io.github.WYRE-AI/alloy-navigator-mcp. MCP server for Alloy Navigator's REST API - IT asset management and ITSM data for MSPs. This page covers its container image (ghcr.io/wyre-ai/alloy-navigator-mcp).

### Is the Alloy Navigator MCP server safe to use?

Alloy Navigator scores 38 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 Alloy Navigator MCP server expose?

Alloy Navigator exposes 4 tools: alloy_list_objects, alloy_get_object, alloy_get_object_activities, alloy_get_dictionary. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.

### Is the Alloy Navigator MCP server still maintained?

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

Alloy Navigator declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/alloy-navigator-mcp
- Repository: https://github.com/WYRE-AI/alloy-navigator-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-alloy-navigator-mcp/ghcr-io-wyre-ai-alloy-navigator-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-alloy-navigator-mcp/ghcr-io-wyre-ai-alloy-navigator-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-alloy-navigator-mcp/ghcr-io-wyre-ai-alloy-navigator-mcp