# Snipe-IT (Mojood Connect) (pypi · mojood-snipeit-mcp)

Snipe-IT assets in Claude: find, audit, check out and in after a yes.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `mojood-snipeit-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp.md), [page](https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp)

## Channel facts

- Registry: `pypi`
- Package: `mojood-snipeit-mcp`
- Version: `0.1.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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to askmojood/snipeit-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 585 tokens (~97/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 current MCP spec version (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 Snipe-IT (Mojood Connect) MCP server?

Snipe-IT (Mojood Connect) runs locally as a PyPI package, launched with uvx mojood-snipeit-mcp --stdio. 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 askmojood-snipeit-mcp -- uvx mojood-snipeit-mcp --stdio
```

### Cursor

```json
{
  "mcpServers": {
    "askmojood-snipeit-mcp": {
      "command": "uvx",
      "args": [
        "mojood-snipeit-mcp",
        "--stdio"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "askmojood-snipeit-mcp": {
      "command": "uvx",
      "args": [
        "mojood-snipeit-mcp",
        "--stdio"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add askmojood-snipeit-mcp -- uvx mojood-snipeit-mcp --stdio
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "askmojood-snipeit-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "mojood-snipeit-mcp",
        "--stdio"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  askmojood-snipeit-mcp:
    command: "uvx"
    args: ["mojood-snipeit-mcp", "--stdio"]
```

### Netclaw

```json
{
  "McpServers": {
    "askmojood-snipeit-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mojood-snipeit-mcp",
        "--stdio"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "askmojood-snipeit-mcp": {
      "command": "uvx",
      "args": [
        "mojood-snipeit-mcp",
        "--stdio"
      ]
    }
  }
}
```

## 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-05 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66)

First indexed and scored.

## MCP tools (6)

### `find_asset` (~71 tokens)

Find an asset

Find assets by tag, serial, model or the name of whoever holds them. Returns status, who has each one,
where it is, its next audit and warranty end.

Input parameters:

- `query` (string, required): an asset tag ("LAP-0142"), serial, model ("ThinkPad") or a person's name

Output parameters:

- `assets` (array)
- `total` (integer): how many match in all; only the first 10 are listed

### `whats_assigned_to` (~60 tokens)

What a person holds

Everything checked out to one person: assets and accessories. If the name matches several people,
returns them as candidates: ask which one.

Input parameters:

- `person` (string, required): a name, e.g. "Sara" or "Sara Al-Qahtani"

Output parameters:

- `accessories` (array)
- `assets` (array)
- `candidates` (array): when more than one person matched: ask which
- `person`: empty when the name matched no one, or more than one person

### `needs_attention` (~47 tokens)

What needs attention

Audits overdue and due, loans overdue and due back soon, warranties ending soon, and assets out of service.

Input parameters:

- `days` (integer): how far ahead to look for returns and warranties

Output parameters:

- `audits_due` (array): due within Snipe-IT's audit warning window
- `audits_overdue` (array)
- `days` (integer)
- `out_of_service` (array): in a status that can't be deployed, e.g. out for repair
- `returns_due` (array): loans due back within `days`
- `returns_overdue` (array): loans past their expected check-in date
- `warranties_ending` (array): warranty ends within `days`

### `low_stock` (~23 tokens)

Low stock

Consumables and accessories below their minimum quantity, with how many are left.

Output parameters:

- `result` (array)

### `check_out_asset` (~110 tokens)

Check out an asset

Assign an asset to a person. The first call changes nothing and returns a summary and a confirmation code;
the change happens only on a second call with the code, after the user has said yes.

Input parameters:

- `asset_tag` (string, required): e.g. "LAP-0160"
- `confirmation`: leave empty first; pass the code only after the user confirms
- `note`: optional, kept in Snipe-IT's history
- `person` (string, required): who it goes to

Output parameters:

- `asset`
- `confirmation`: when done is false: the code to pass back, only after the user says yes
- `done` (boolean): false: nothing has changed yet; true: Snipe-IT has made the change
- `expires_in_minutes`
- `problem`: why it can't be done; nothing was changed
- `summary` (string)

### `check_in_asset` (~101 tokens)

Check in an asset

Return an asset from whoever holds it. The first call changes nothing and returns a summary and a
confirmation code; the change happens only on a second call with the code, after the user has said yes.

Input parameters:

- `asset_tag` (string, required): e.g. "LAP-0162"
- `confirmation`: leave empty first; pass the code only after the user confirms
- `note`: optional, kept in Snipe-IT's history

Output parameters:

- `asset`
- `confirmation`: when done is false: the code to pass back, only after the user says yes
- `done` (boolean): false: nothing has changed yet; true: Snipe-IT has made the change
- `expires_in_minutes`
- `problem`: why it can't be done; nothing was changed
- `summary` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 66

## Common questions

### What is the Snipe-IT (Mojood Connect) MCP server?

Snipe-IT (Mojood Connect) is an MCP server listed in the public MCP registry as io.github.askmojood/snipeit-mcp. Snipe-IT assets in Claude: find, audit, check out and in after a yes. This page covers its PyPI package (mojood-snipeit-mcp).

### Is the Snipe-IT (Mojood Connect) MCP server safe to use?

Snipe-IT (Mojood Connect) scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Snipe-IT (Mojood Connect) MCP server expose?

Snipe-IT (Mojood Connect) exposes 6 tools: find_asset, whats_assigned_to, needs_attention, low_stock, check_out_asset, check_in_asset. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.

### Is the Snipe-IT (Mojood Connect) MCP server still maintained?

Snipe-IT (Mojood Connect) is still listed as active in the MCP registry. We last reached this channel on 5 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 Snipe-IT (Mojood Connect) MCP server under?

Snipe-IT (Mojood Connect) 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 Snipe-IT (Mojood Connect) MCP server?

VerifyMCP ran 15 checks on Snipe-IT (Mojood Connect), covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Snipe-IT (Mojood Connect): Stability. 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 PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/mojood-snipeit-mcp/
- Socket report: https://socket.dev/pypi/package/mojood-snipeit-mcp
- Repository: https://github.com/askmojood/snipeit-mcp
- Website: https://mojood.app/connect
- Changelog RSS feed: https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/askmojood-snipeit-mcp/mojood-snipeit-mcp