Swsd MCP Server

swsd-mcp npm v2.3.1 Source verified

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

MCP server for SolarWinds Service Desk (SWSD / Samanage). Dual transport: stdio for local agents, Streamable HTTP for Copilot Studio and hosted deployments. Not affiliated with SolarWinds.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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
Moderate
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 = 97/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 − 3 = 97. 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
−3 capability blast radius (moderate) — 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 31

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

  • swsd_get_problemingests untrusted input
  • swsd_add_incident_commentno sensitive capability
  • swsd_assign_incidentno sensitive capability
  • swsd_create_incidentno sensitive capability
  • swsd_create_incident_taskno sensitive capability
  • swsd_create_problemno sensitive capability
  • swsd_create_service_requestno sensitive capability
  • swsd_create_solutionno sensitive capability
  • swsd_get_meno sensitive capability
  • swsd_get_server_infono sensitive capability
Show 21 more tools ↓
  • swsd_health_checkno sensitive capability
  • swsd_link_solution_to_incidentno sensitive capability
  • swsd_list_catalog_itemsno sensitive capability
  • swsd_list_categoriesno sensitive capability
  • swsd_list_departmentsno sensitive capability
  • swsd_list_groupsno sensitive capability
  • swsd_list_incident_tasksno sensitive capability
  • swsd_list_problemsno sensitive capability
  • swsd_list_rolesno sensitive capability
  • swsd_list_sitesno sensitive capability
  • swsd_list_time_tracksno sensitive capability
  • swsd_list_usersno sensitive capability
  • swsd_log_timeno sensitive capability
  • swsd_search_solutionsno sensitive capability
  • swsd_update_commentno sensitive capability
  • swsd_update_incidentno sensitive capability
  • swsd_update_incident_stateno sensitive capability
  • swsd_update_solutionno sensitive capability
  • swsd_update_task_stateno sensitive capability
  • swsd_update_time_trackno sensitive capability
  • swsd_upload_attachmentno sensitive capability

What this scan could not see

Versions 4

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
v2.3.1 latest A 97/100 0 1.13.0 2026-09-07
v2.3.0 A 97/100 0 1.12.1 2026-08-20
v2.2.1 A 97/100 0 1.12.1 2026-08-10
v2.2.0 A 97/100 0 1.12.1 2026-08-03

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

Use the free API → How scoring works

More in Business & CRM