ServiceNow
NPM · @MINDSTONE/MCP-SERVER-SERVICENOW · SCANNED AUG 6
ServiceNow ITSM MCP server for Model Context Protocol hosts
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 Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
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 (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 79 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mindstone/mcp-server-servicenow
claude mcp add mindstone-mcp-server-servicenow -- npx -y @mindstone/mcp-server-servicenow
codex mcp add mindstone-mcp-server-servicenow -- npx -y @mindstone/mcp-server-servicenow
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindstone-mcp-server-servicenow": {
"type": "local",
"command": [
"npx",
"-y",
"@mindstone/mcp-server-servicenow"
],
"enabled": true
}
}
} openclaw mcp add mindstone-mcp-server-servicenow --command npx --arg -y --arg @mindstone/mcp-server-servicenow
mcp_servers:
mindstone-mcp-server-servicenow:
command: "npx"
args: ["-y", "@mindstone/mcp-server-servicenow"] {
"mcpServers": {
"mindstone-mcp-server-servicenow": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-servicenow"
]
}
}
} 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.
- 6 Aug 26 +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.
- 5 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 +3
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +37
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → fail ▼ functional
- Schema quality: unverified → good ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: FSL-1.1-MIT functional
- 31 Jul 26 −20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 45
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 6 Aug 2026 · Analysed npm/@mindstone/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Deprecated | 95 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
configure_servicenow ~158
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).
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | yes | ServiceNow instance name (e.g., "acme") or full URL (e.g., "https://acme.service-now.com") |
| password | string | yes | ServiceNow password |
| username | string | yes | ServiceNow username |
No output schema declared.
No examples provided.
create_servicenow_incident ~174
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Brief description of the incident |
| urgency | string | – | Urgency: "1" (High), "2" (Medium), "3" (Low) |
No output schema declared.
No examples provided.
get_servicenow_change_request ~66
Get a single change request by number (e.g., CHG0010001) or sys_id. Returns the full change request record with all fields.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Change request number (e.g., CHG0010001) or sys_id |
No output schema declared.
No examples provided.
get_servicenow_incident ~61
Get a single incident by number (e.g., INC0010001) or sys_id. Returns the full incident record with all fields.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Incident number (e.g., INC0010001) or sys_id |
No output schema declared.
No examples provided.
get_servicenow_knowledge_article ~66
Get a full knowledge base article by sys_id or number (e.g., KB0010001). Returns the full article record including the article body text.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | KB article number (e.g., KB0010001) or sys_id |
No output schema declared.
No examples provided.
list_servicenow_change_requests ~119
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
list_servicenow_incidents ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
list_servicenow_users ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
search_servicenow_knowledge ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (default: 20) |
| offset | number | – | Offset for pagination (default: 0) |
| query | string | – | Search keywords or ServiceNow encoded query |
No output schema declared.
No examples provided.
update_servicenow_incident ~260
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Incident sys_id (use get_servicenow_incident to find it) |
| urgency | string | – | Urgency: "1" (High), "2" (Medium), "3" (Low) |
No output schema declared.
No examples provided.