# ServiceNow (npm · @mindstone/mcp-server-servicenow)

ServiceNow ITSM MCP server for Model Context Protocol hosts

- Trust score: 67/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-06

## Components

- npm · `@mindstone/mcp-server-servicenow`: 67/100 (this document), [markdown](https://verifymcp.io/servers/mindstone-mcp-server-servicenow/mindstone-mcp-server-servicenow.md), [page](https://verifymcp.io/servers/mindstone-mcp-server-servicenow/mindstone-mcp-server-servicenow)

## Channel facts

- Registry: `npm`
- Package: `@mindstone/mcp-server-servicenow`
- Version: `0.2.2`
- 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-08-06.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **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 (FSL-1.1-MIT) isn't a recognized OSI-approved license.
  - Actively maintained (last published 79 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1261 tokens (~126/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mindstone-mcp-server-servicenow -- npx -y @mindstone/mcp-server-servicenow
```

### Codex

```bash
codex mcp add mindstone-mcp-server-servicenow -- npx -y @mindstone/mcp-server-servicenow
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mindstone-mcp-server-servicenow": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mindstone/mcp-server-servicenow"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mindstone-mcp-server-servicenow --command npx --arg -y --arg @mindstone/mcp-server-servicenow
```

### Hermes

```yaml
mcp_servers:
  mindstone-mcp-server-servicenow:
    command: "npx"
    args: ["-y", "@mindstone/mcp-server-servicenow"]
```

### Other

```json
{
  "mcpServers": {
    "mindstone-mcp-server-servicenow": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-servicenow"
      ]
    }
  }
}
```

## 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-08-06 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-05 (score 66, +1)

- [security improvement] CVE-2026-69207 no longer affects this package
- [security improvement] Known CVEs: fail → partial

### 2026-08-04 (score 65, +3)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail
- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 62, +37)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] License: unverified → fail
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional] Licence: FSL-1.1-MIT

### 2026-07-31 (score 25, −20)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 45)

First indexed and scored.

## MCP tools (10)

### `configure_servicenow` (~158 tokens)

Configure ServiceNow credentials. Call this when the user provides their instance name, username, and password. The instance name is the subdomain part of the URL (e.g., "acme" for acme.service-now.com). You can also paste the full URL. The account needs read/write access to incident, change_request, kb_knowledge, and sys_user tables. For production use, consider creating a dedicated integration user with appropriate roles (itil, knowledge).

Input parameters:

- `instance` (string, required): ServiceNow instance name (e.g., "acme") or full URL (e.g., "https://acme.service-now.com")
- `password` (string, required): ServiceNow password
- `username` (string, required): ServiceNow username

### `list_servicenow_incidents` (~127 tokens)

List or search incidents in ServiceNow. Returns: number, short_description, state, priority, assigned_to, sys_created_on, sys_updated_on, urgency, impact. Use ServiceNow encoded query syntax for filtering (^ as AND separator). Use get_servicenow_incident for full details of a specific incident.

Input parameters:

- `limit` (number): Max results to return (default: 20)
- `offset` (number): Offset for pagination (default: 0)
- `query` (string): ServiceNow encoded query (e.g., "active=true^priority=1")

### `get_servicenow_incident` (~61 tokens)

Get a single incident by number (e.g., INC0010001) or sys_id. Returns the full incident record with all fields.

Input parameters:

- `identifier` (string, required): Incident number (e.g., INC0010001) or sys_id

### `create_servicenow_incident` (~174 tokens)

Create a new incident in ServiceNow. Provide at minimum a short_description. Set urgency and impact to control priority (1=High, 2=Medium, 3=Low). Note: urgency and impact are strings "1", "2", "3".

Input parameters:

- `assignment_group` (string): Assignment group name
- `caller_id` (string): Caller user name or sys_id
- `category` (string): Incident category
- `description` (string): Detailed description
- `impact` (string): Impact: "1" (High), "2" (Medium), "3" (Low)
- `short_description` (string, required): Brief description of the incident
- `urgency` (string): Urgency: "1" (High), "2" (Medium), "3" (Low)

### `update_servicenow_incident` (~260 tokens)

Update an existing incident in ServiceNow by sys_id. Use get_servicenow_incident to find the sys_id first. State values: "1" (New), "2" (In Progress), "3" (On Hold), "6" (Resolved), "7" (Closed).

Input parameters:

- `assigned_to` (string): Assigned to user name or sys_id
- `assignment_group` (string): Assignment group name
- `close_code` (string): Close code (required when resolving)
- `close_notes` (string): Close notes (required when resolving)
- `description` (string): Detailed description
- `impact` (string): Impact: "1" (High), "2" (Medium), "3" (Low)
- `short_description` (string): Brief description
- `state` (string): State: "1" (New), "2" (In Progress), "3" (On Hold), "6" (Resolved), "7" (Closed)
- `sys_id` (string, required): Incident sys_id (use get_servicenow_incident to find it)
- `urgency` (string): Urgency: "1" (High), "2" (Medium), "3" (Low)

### `list_servicenow_change_requests` (~119 tokens)

List or search change requests in ServiceNow. Returns: number, short_description, state, type, priority, assigned_to, start_date, end_date. Use ServiceNow encoded query syntax for filtering. Type values: "normal", "standard", "emergency".

Input parameters:

- `limit` (number): Max results to return (default: 20)
- `offset` (number): Offset for pagination (default: 0)
- `query` (string): ServiceNow encoded query (e.g., "state=implement^type=normal")

### `get_servicenow_change_request` (~66 tokens)

Get a single change request by number (e.g., CHG0010001) or sys_id. Returns the full change request record with all fields.

Input parameters:

- `identifier` (string, required): Change request number (e.g., CHG0010001) or sys_id

### `search_servicenow_knowledge` (~108 tokens)

Search knowledge base articles in ServiceNow. Returns: number, short_description, sys_created_on, author, kb_knowledge_base, workflow_state. Simple text queries are automatically converted to LIKE queries. For advanced filtering, use ServiceNow encoded query syntax directly.

Input parameters:

- `limit` (number): Max results to return (default: 20)
- `offset` (number): Offset for pagination (default: 0)
- `query` (string): Search keywords or ServiceNow encoded query

### `get_servicenow_knowledge_article` (~66 tokens)

Get a full knowledge base article by sys_id or number (e.g., KB0010001). Returns the full article record including the article body text.

Input parameters:

- `identifier` (string, required): KB article number (e.g., KB0010001) or sys_id

### `list_servicenow_users` (~122 tokens)

List or search users in ServiceNow. Returns: sys_id, user_name, first_name, last_name, email, title, department, active. user_name is the login username, not the display name. For name searches, use first_nameLIKE or last_nameLIKE in the query.

Input parameters:

- `limit` (number): Max results to return (default: 20)
- `offset` (number): Offset for pagination (default: 0)
- `query` (string): ServiceNow encoded query (e.g., "active=true^departmentLIKEengineering")

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mindstone-mcp-server-servicenow/mindstone-mcp-server-servicenow#diagnostics

## Score history

- 2026-08-06: 67
- 2026-08-05: 66
- 2026-08-04: 65
- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 25
- 2026-07-31: 25
- 2026-07-30: 45
- 2026-07-28: 45
- 2026-07-27: 45

## Links

- npm package: https://www.npmjs.com/package/@mindstone/mcp-server-servicenow
- Socket report: https://socket.dev/npm/package/@mindstone/mcp-server-servicenow
- Repository: https://github.com/mindstone/mcp-servers
- Changelog RSS feed: https://verifymcp.io/servers/mindstone-mcp-server-servicenow/mindstone-mcp-server-servicenow.xml
- Changelog JSON feed: https://verifymcp.io/servers/mindstone-mcp-server-servicenow/mindstone-mcp-server-servicenow.json
- HTML version of this page: https://verifymcp.io/servers/mindstone-mcp-server-servicenow/mindstone-mcp-server-servicenow