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.
Available components
Last scanned (10 hours ago)
Scores higher than 51% of OCI servers
Category Project Management
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 → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
- 18 Oct 26 +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.
- 17 Oct 26 37
First indexed and scored.
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 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/alloy-navigator-mcp@v1.0.1
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 |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
alloy_get_dictionary ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The reference field name, e.g. 'Status' or 'Types'. |
No output schema declared.
No examples provided.
alloy_get_object ~57
Get every field of a single Alloy Navigator object by its OID (e.g. a ticket number like T000002) or database record GUID.
| Name | Type | Req | Description |
|---|---|---|---|
| oid | string | yes | The object's OID or GUID (from alloy_list_objects). |
No output schema declared.
No examples provided.
alloy_get_object_activities ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| oid | string | yes | 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. |
No output schema declared.
No examples provided.
alloy_list_objects ~310
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/wyre-ai/alloy-navigator-mcp
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.
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.