Axis (hemla) MCP Server

@hemla/axis-mcp npm v0.2.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 Axis IP cameras via VAPIX

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 37

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

  • add_text_overlayno sensitive capability
  • connect_camerano sensitive capability
  • create_stream_profileno sensitive capability
  • create_userno sensitive capability
  • discover_apisno sensitive capability
  • factory_defaultno sensitive capability
  • get_access_logno sensitive capability
  • get_capture_modeno sensitive capability
  • get_datetimeno sensitive capability
  • get_device_infono sensitive capability
Show 27 more tools ↓
  • get_image_settingsno sensitive capability
  • get_network_configno sensitive capability
  • get_network_infono sensitive capability
  • get_ntpno sensitive capability
  • get_overlayno sensitive capability
  • get_ptz_positionno sensitive capability
  • get_ptz_presetsno sensitive capability
  • get_server_reportno sensitive capability
  • get_snapshotno sensitive capability
  • get_storage_infono sensitive capability
  • get_stream_profilesno sensitive capability
  • get_system_logno sensitive capability
  • get_usersno sensitive capability
  • goto_ptz_presetno sensitive capability
  • ptz_moveno sensitive capability
  • reboot_camerano sensitive capability
  • remove_overlayno sensitive capability
  • remove_stream_profileno sensitive capability
  • remove_userno sensitive capability
  • set_datetimeno sensitive capability
  • set_image_settingsno sensitive capability
  • set_network_configno sensitive capability
  • set_ntpno sensitive capability
  • set_ptz_positionno sensitive capability
  • setup_initial_userno sensitive capability
  • update_stream_profileno 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.2.1 latest A 99/100 0 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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/hemla-axis-mcp/badge.svg)](https://mcptrustchecker.com/registry/hemla-axis-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/hemla-axis-mcp"><img src="https://mcptrustchecker.com/registry/hemla-axis-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/hemla-axis-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/axis-mcp --online

Use the free API → How scoring works

Other implementations of Axis 1

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

More in API Development