@kieksme/listmonk-mcp — MCP security scan

Scan results for @kieksme/listmonk-mcp

Scanned · engine 1.13.0
@kieksme/listmonk-mcp npm v1.3.0 Source verified
A
100/100
Trust
A · 100/100
adoption risk
Capability
Minimal
blast radius
Coverage
source
how much was read
Share this result
Embed the badge
MCP Trust Score A
[![MCP Trust Score](https://mcptrustchecker.com/scan/npm/%40kieksme%2Flistmonk-mcp/badge.svg)](https://mcptrustchecker.com/scan/npm/%40kieksme%2Flistmonk-mcp)
<a href="https://mcptrustchecker.com/scan/npm/%40kieksme%2Flistmonk-mcp"><img src="https://mcptrustchecker.com/scan/npm/%40kieksme%2Flistmonk-mcp/badge.svg" alt="MCP Trust Score"></a>

This badge scans live on each load. Add it to the registry for a cached, canonical badge and a public page.

A Why this grade threat 100 − adoption risk = 100/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 − 0 = 100. 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:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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.
Scan another server → Browse the registry →