NinjaOne
OCI · GHCR.IO/WYRE-TECHNOLOGY/NINJAONE-MCP:V2.2.9 · SCANNED AUG 22
MCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.
Available components
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 →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
- 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
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1397 tokens (~53/item across 26 items; 25 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 19% of tool parameters carry a description.Partial
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Unverified: 2 categories
Categories scored 0 because we could not verify them: 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.
How do I install the NinjaOne MCP server?
NinjaOne runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9. 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-technology/ninjaone-mcp:v2.2.9
claude mcp add wyre-technology-ninjaone-mcp -- docker run --rm -i ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9
{
"mcpServers": {
"wyre-technology-ninjaone-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"
]
}
}
} {
"servers": {
"wyre-technology-ninjaone-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"
]
}
}
} codex mcp add wyre-technology-ninjaone-mcp -- docker run --rm -i ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wyre-technology-ninjaone-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"
],
"enabled": true
}
}
} mcp_servers:
wyre-technology-ninjaone-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"] {
"McpServers": {
"wyre-technology-ninjaone-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"
]
}
}
} {
"mcpServers": {
"wyre-technology-ninjaone-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"
]
}
}
} 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.
- 21 Aug 26 38
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 22 Aug 2026 · Analysed oci/ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9
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 |
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.
ninjaone_alerts_get ~29
Get details for a specific alert by its UID
| Name | Type | Req | Description |
|---|---|---|---|
| alert_uid | string | yes | – |
No output schema declared.
No examples provided.
ninjaone_alerts_list ~77
List active alerts, filterable by severity, organization, or device
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| device_id | number | – | – |
| limit | number | – | – |
| organization_id | number | – | – |
| severity | string | – | – |
| source_type | string | – | e.g., CONDITION, ACTIVITY |
No output schema declared.
No examples provided.
ninjaone_alerts_reset ~32
Reset (dismiss) an alert - acknowledges and marks as handled
| Name | Type | Req | Description |
|---|---|---|---|
| alert_uid | string | yes | – |
No output schema declared.
No examples provided.
ninjaone_alerts_reset_all ~48
Reset all alerts for a device or organization (destructive action)
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | – | – |
| organization_id | number | – | – |
| severity | string | – | – |
No output schema declared.
No examples provided.
ninjaone_alerts_summary ~30
Get alert count summary grouped by severity and/or organization
| Name | Type | Req | Description |
|---|---|---|---|
| group_by | string | – | – |
No output schema declared.
No examples provided.
ninjaone_devices_activities ~39
Get device activity log
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type | string | – | – |
| device_id | number | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
ninjaone_devices_alerts ~33
Get active alerts for a device
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | – |
| severity | string | – | – |
No output schema declared.
No examples provided.
ninjaone_devices_get ~24
Get device details by ID
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_devices_list ~98
List NinjaOne devices, filterable by organization, device class, or online status
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response's cursor field (the last device id). |
| device_class | string | – | – |
| limit | number | – | Max devices to return (default 50). A full page sets hasMore=true and returns a cursor. |
| online | boolean | – | – |
| organization_id | number | – | – |
No output schema declared.
No examples provided.
ninjaone_devices_reboot ~34
Schedule device reboot (destructive action)
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
ninjaone_devices_services ~32
List Windows services on a device
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | number | yes | – |
| state | string | – | – |
No output schema declared.
No examples provided.
ninjaone_navigate ~135
Discover available NinjaOne tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to explore: - devices: Device management - manage endpoints, reboot systems, view services, and get device alerts/activities - organizations: Organization management - manage customer acco… |
No output schema declared.
No examples provided.
ninjaone_organizations_create ~53
Create new organization
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
| node_approval_mode | string | – | How to handle new device registrations |
| policy_id | number | – | – |
No output schema declared.
No examples provided.
ninjaone_organizations_devices ~38
List organization devices
| Name | Type | Req | Description |
|---|---|---|---|
| device_class | string | – | – |
| limit | number | – | – |
| organization_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_organizations_get ~25
Get organization details by ID
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_organizations_list ~31
List organizations (customer accounts)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
ninjaone_organizations_locations ~23
List organization locations
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_status ~18
Show API credential status and available tool domains
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ninjaone_tickets_add_comment ~46
Add comment to ticket
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| public | boolean | – | visible to customers (default: true) |
| ticket_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_tickets_boards_list ~35
List available ticket boards for the tenant. Use this to discover board_id values for ninjaone_tickets_list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ninjaone_tickets_comments ~25
Get ticket comments and activity
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_tickets_create ~67
Create new ticket
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | number | – | – |
| description | string | – | – |
| device_id | number | – | – |
| organization_id | number | yes | – |
| priority | string | – | – |
| subject | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
ninjaone_tickets_get ~25
Get ticket details by ID
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | number | yes | – |
No output schema declared.
No examples provided.
ninjaone_tickets_list ~323
List tickets from a ticket board, filterable by status, organization, or device. Requires board_id: NinjaOne queries tickets per board and board IDs vary by tenant (board 1 is NOT always the 'All Tickets' board). Discover board IDs with ninjaone_tickets_boards_list first. NOTE: status/organization/device filters are applied client-side within one board page (NinjaOne's board API cannot filter by them server-side), so the response reports `count` (matches in this page) separately from `scanned`, plus `hasMore`/`cursor` — page through until hasMore is false to get every match; never treat one page's count as a board-wide total.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | number | yes | Ticket board to query. Use ninjaone_tickets_boards_list to discover valid IDs; if that endpoint is unavailable on your tenant, read the ID from the board's URL in the NinjaOne web UI. |
| cursor | string | – | Pagination cursor from a previous response's cursor field (the board's lastCursorId). |
| device_id | number | – | Filter by linked device (ticket nodeId), matched client-side. |
| limit | number | – | Board page size (default 50). A full page sets hasMore=true and returns a cursor. |
| organization_id | number | – | Filter by organization (ticket clientId), matched client-side. |
| status | string | – | Filter by status, matched client-side against each ticket's status display name. Custom board statuses whose names differ from these values won't match. |
No output schema declared.
No examples provided.
ninjaone_tickets_update ~60
Update existing ticket
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | number | – | – |
| description | string | – | – |
| priority | string | – | – |
| status | string | – | – |
| subject | string | – | – |
| ticket_id | number | yes | – |
No output schema declared.
No examples provided.
What is the NinjaOne MCP server?
NinjaOne is an MCP server listed in the public MCP registry as io.github.wyre-technology/ninjaone-mcp. MCP server for NinjaOne RMM, devices, organizations, alerts, and tickets. This page covers its container image (ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9).
Is the NinjaOne MCP server safe to use?
NinjaOne 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 NinjaOne MCP server expose?
NinjaOne exposes 25 tools: ninjaone_navigate, ninjaone_status, ninjaone_devices_list, ninjaone_devices_get, ninjaone_devices_reboot, and 20 more. Their descriptions and schemas cost roughly 1,380 tokens of context every time the server is loaded.
Is the NinjaOne MCP server still maintained?
NinjaOne is still listed as active in the MCP registry. We last reached this channel on 22 August 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 NinjaOne MCP server under?
NinjaOne 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.