Now Sdk Ext MCP Server

@sonisoft/now-sdk-ext-mcp npm v4.8.1 Source verified

Published by sonisoft-cnanda — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for interacting with ServiceNow instances via @sonisoft/now-sdk-ext-core

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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 = 94/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 − 6 = 94. 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

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 9

high Tool "pull_script" exposes command/code executionMTC-CAP-001

Tool "pull_script" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool pull_script

high Tool "push_script" exposes command/code executionMTC-CAP-001

Tool "push_script" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool push_script

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

Untrusted-input tools ([search_store_apps]) co-exist with external-action tools ([pull_script, push_script]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [search_store_apps] → sinks [pull_script, push_script]

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

Location: flow search_store_apps → pull_script

medium Unconstrained command parameter "script_name" on "pull_script"MTC-CAP-006

Tool "pull_script" takes a command-shaped parameter "script_name" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool pull_script · inputSchema.properties.script_name

medium Unconstrained command parameter "script_type" on "pull_script"MTC-CAP-006

Tool "pull_script" takes a command-shaped parameter "script_type" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool pull_script · inputSchema.properties.script_type

medium Unconstrained command parameter "script_name" on "push_script"MTC-CAP-006

Tool "push_script" takes a command-shaped parameter "script_name" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool push_script · inputSchema.properties.script_name

medium Unconstrained command parameter "script_type" on "push_script"MTC-CAP-006

Tool "push_script" takes a command-shaped parameter "script_type" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool push_script · inputSchema.properties.script_type

low Mutating tool "pull_script" declares no destructiveHintMTC-CAP-005

Tool "pull_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool pull_script

low Mutating tool "push_script" declares no destructiveHintMTC-CAP-005

Tool "push_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool push_script

Tools 89

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

  • pull_scriptruns code / shell
  • push_scriptruns code / shell
  • search_store_appsingests untrusted input
  • add_code_search_tableno sensitive capability
  • add_task_commentno sensitive capability
  • aggregate_groupedno sensitive capability
  • aggregate_queryno sensitive capability
  • approve_changeno sensitive capability
  • assign_taskno sensitive capability
  • batch_create_recordsno sensitive capability
Show 79 more tools ↓
  • batch_update_recordsno sensitive capability
  • cancel_flowno sensitive capability
  • check_instance_healthno sensitive capability
  • clone_update_setno sensitive capability
  • close_incidentno sensitive capability
  • code_searchno sensitive capability
  • copy_flowno sensitive capability
  • count_recordsno sensitive capability
  • create_kb_articleno sensitive capability
  • create_kb_categoryno sensitive capability
  • create_update_setno sensitive capability
  • create_workflowno sensitive capability
  • discover_table_behaviorno sensitive capability
  • discover_table_schemano sensitive capability
  • execute_actionno sensitive capability
  • execute_flowno sensitive capability
  • execute_scriptno sensitive capability
  • execute_subflowno sensitive capability
  • explain_fieldno sensitive capability
  • export_record_xmlno sensitive capability
  • find_atf_testsno sensitive capability
  • find_taskno sensitive capability
  • get_app_detailsno sensitive capability
  • get_attachment_infono sensitive capability
  • get_behavior_detailsno sensitive capability
  • get_catalog_categoryno sensitive capability
  • get_catalog_itemno sensitive capability
  • get_cmdb_relationshipsno sensitive capability
  • get_current_scopeno sensitive capability
  • get_current_update_setno sensitive capability
  • get_flow_context_statusno sensitive capability
  • get_flow_errorno sensitive capability
  • get_flow_execution_detailsno sensitive capability
  • get_flow_logsno sensitive capability
  • get_flow_outputsno sensitive capability
  • get_kb_articleno sensitive capability
  • get_knowledge_baseno sensitive capability
  • import_records_xmlno sensitive capability
  • inspect_update_setno sensitive capability
  • install_from_app_repono sensitive capability
  • install_store_appno sensitive capability
  • list_attachmentsno sensitive capability
  • list_catalog_categoriesno sensitive capability
  • list_catalog_item_variablesno sensitive capability
  • list_catalog_itemsno sensitive capability
  • list_code_search_groupsno sensitive capability
  • list_code_search_tablesno sensitive capability
  • list_company_appsno sensitive capability
  • list_instance_tablesno sensitive capability
  • list_kb_articlesno sensitive capability
  • list_kb_categoriesno sensitive capability
  • list_knowledge_basesno sensitive capability
  • list_pluginsno sensitive capability
  • list_scoped_appsno sensitive capability
  • list_tool_packagesno sensitive capability
  • list_update_setsno sensitive capability
  • lookup_appno sensitive capability
  • lookup_columnsno sensitive capability
  • lookup_tableno sensitive capability
  • move_update_set_recordsno sensitive capability
  • publish_kb_articleno sensitive capability
  • publish_to_app_repono sensitive capability
  • query_delete_recordsno sensitive capability
  • query_syslogno sensitive capability
  • query_tableno sensitive capability
  • query_update_recordsno sensitive capability
  • resolve_incidentno sensitive capability
  • run_atf_testno sensitive capability
  • run_atf_test_suiteno sensitive capability
  • set_current_scopeno sensitive capability
  • set_current_update_setno sensitive capability
  • submit_catalog_requestno sensitive capability
  • test_flowno sensitive capability
  • traverse_cmdb_graphno sensitive capability
  • update_kb_articleno sensitive capability
  • update_store_appno sensitive capability
  • upload_attachmentno sensitive capability
  • validate_app_installno sensitive capability
  • validate_catalogno 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 5

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
v4.8.1 latest A 94/100 9 1.13.0 2026-09-07
v4.7.1 A 94/100 9 1.13.0 2026-09-05
v4.7.0 A 94/100 9 1.13.0 2026-08-28
v4.5.0 A 94/100 9 1.12.1 2026-08-05
v2.5.1 A 94/100 9 1.12.1 2026-07-29

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 · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sonisoft-now-sdk-ext-mcp/badge.svg)](https://mcptrustchecker.com/registry/sonisoft-now-sdk-ext-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/sonisoft-now-sdk-ext-mcp"><img src="https://mcptrustchecker.com/registry/sonisoft-now-sdk-ext-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sonisoft-now-sdk-ext-mcp/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 @sonisoft/now-sdk-ext-mcp --online

Use the free API → How scoring works

More in Cloud & DevOps