Hanwha MCP Server

@hemla/hanwha-mcp npm v0.3.1

Published by @hemla — 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 configuring Hanwha Vision IP cameras via SUNAPI

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

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

Tools 43

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

  • get_logsreads sensitive data
  • add_video_profileno sensitive capability
  • connect_camerano sensitive capability
  • create_userno sensitive capability
  • get_datetimeno sensitive capability
  • get_defocus_detectionno sensitive capability
  • get_device_infono sensitive capability
  • get_event_rulesno sensitive capability
  • get_image_settingsno sensitive capability
  • get_network_configno sensitive capability
Show 33 more tools ↓
  • get_network_infono sensitive capability
  • get_osd_listno sensitive capability
  • get_overlayno sensitive capability
  • get_privacy_maskno sensitive capability
  • get_snapshotno sensitive capability
  • get_ssdrno sensitive capability
  • get_storage_configno sensitive capability
  • get_tampering_detectionno sensitive capability
  • get_usersno sensitive capability
  • get_video_profilesno sensitive capability
  • get_white_balanceno sensitive capability
  • reboot_camerano sensitive capability
  • remove_osdno sensitive capability
  • remove_userno sensitive capability
  • remove_video_profileno sensitive capability
  • set_datetimeno sensitive capability
  • set_defocus_detectionno sensitive capability
  • set_event_ruleno sensitive capability
  • set_flipno sensitive capability
  • set_focusno sensitive capability
  • set_image_settingsno sensitive capability
  • set_ir_ledno sensitive capability
  • set_network_configno sensitive capability
  • set_ntpno sensitive capability
  • set_osdno sensitive capability
  • set_overlayno sensitive capability
  • set_privacy_maskno sensitive capability
  • set_ssdrno sensitive capability
  • set_storage_configno sensitive capability
  • set_tampering_detectionno sensitive capability
  • set_video_profileno sensitive capability
  • set_white_balanceno sensitive capability
  • update_userno sensitive capability

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

Use the free API → How scoring works

More in Security & Testing