Servicenow (autopilot715) MCP Server

@autopilot715/servicenow-mcp-server npm v1.0.4

Published by @autopilot715 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for ServiceNow — incidents, changes, CMDB, service catalog, users, and knowledge base

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/services/auth.js)MTC-SRC-002

In the server's implementation (`dist/services/auth.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ort { exec } from "node:child_process"; // ── Mode detection ──────────────────────────── export function detectAuthMode

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/services/auth.js

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([servicenow_list_attachments, servicenow_get_attachment_content, servicenow_upload_attachment, servicenow_list_catalog_items]) co-exist with external-action tools ([servicenow_query_records]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [servicenow_list_attachments, servicenow_get_attachment_content, servicenow_upload_attachment, servicenow_list_catalog_items] → sinks [servicenow_quer

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow servicenow_list_attachments → servicenow_query_records

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • servicenow_get_attachment_contentingests untrusted input
  • servicenow_list_attachmentsingests untrusted input
  • servicenow_list_catalog_itemsingests untrusted input
  • servicenow_query_recordsnetwork egress
  • servicenow_upload_attachmentingests untrusted input
  • servicenow_add_work_noteno sensitive capability
  • servicenow_aggregateno sensitive capability
  • servicenow_bulk_deleteno sensitive capability
  • servicenow_bulk_updateno sensitive capability
  • servicenow_create_changeno sensitive capability
Show 31 more tools ↓
  • servicenow_create_incidentno sensitive capability
  • servicenow_create_recordno sensitive capability
  • servicenow_delete_recordno sensitive capability
  • servicenow_discover_tablesno sensitive capability
  • servicenow_get_catalog_itemno sensitive capability
  • servicenow_get_changeno sensitive capability
  • servicenow_get_cino sensitive capability
  • servicenow_get_ci_relationshipsno sensitive capability
  • servicenow_get_group_membersno sensitive capability
  • servicenow_get_incidentno sensitive capability
  • servicenow_get_instance_infono sensitive capability
  • servicenow_get_kb_articleno sensitive capability
  • servicenow_get_recordno sensitive capability
  • servicenow_get_table_schemano sensitive capability
  • servicenow_get_userno sensitive capability
  • servicenow_list_applicationsno sensitive capability
  • servicenow_list_atf_testsno sensitive capability
  • servicenow_list_changesno sensitive capability
  • servicenow_list_groupsno sensitive capability
  • servicenow_list_incidentsno sensitive capability
  • servicenow_list_sc_requestsno sensitive capability
  • servicenow_list_usersno sensitive capability
  • servicenow_query_logsno sensitive capability
  • servicenow_run_atf_testno sensitive capability
  • servicenow_search_artifactsno sensitive capability
  • servicenow_search_cino sensitive capability
  • servicenow_search_knowledgeno sensitive capability
  • servicenow_submit_catalog_requestno sensitive capability
  • servicenow_update_changeno sensitive capability
  • servicenow_update_incidentno sensitive capability
  • servicenow_update_recordno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.4 latest A 93/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/autopilot715-servicenow-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/autopilot715-servicenow-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/autopilot715-servicenow-mcp-server"><img src="https://mcptrustchecker.com/registry/autopilot715-servicenow-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/autopilot715-servicenow-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @autopilot715/servicenow-mcp-server --online

Use the free API → How scoring works

Other implementations of Servicenow 8

Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →

More in AI, Memory & Reasoning