Llng MCP Server

llng-mcp npm v0.2.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP Server for Lemonldap-NG

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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 = 92/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 − 8 = 92. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 6

high Shell/command execution in server code (dist/transport/k8s.js)MTC-SRC-002

In the server's implementation (`dist/transport/k8s.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from "child_process"; import { resolvePaths } from "../config.js"; export class K8sTransport { con

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/transport/k8s.js

high Shell/command execution in server code (dist/transport/ssh.js)MTC-SRC-002

In the server's implementation (`dist/transport/ssh.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from "child_process"; import { resolvePaths } from "../config.js"; export class SshTransport { con

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/transport/ssh.js

low Shell/command execution in packaging/dev tooling (dist/__tests__/integration/oidc-rp.test.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/__tests__/integration/oidc-rp.test.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from "child_process"; describe("OIDC RP Integration (via docker exec)", () => { let available = fa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/__tests__/integration/oidc-rp.test.js

low Shell/command execution in packaging/dev tooling (dist/__tests__/integration/ssh-mode.test.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/__tests__/integration/ssh-mode.test.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from "child_process"; describe("SSH Transport Integration (via docker exec)", () => { let availabl

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/__tests__/integration/ssh-mode.test.js

low Shell/command execution in packaging/dev tooling (dist/__tests__/k8s-transport.test.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/__tests__/k8s-transport.test.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt/k8s.js"; import * as child_process from "child_process"; import { EventEmitter } from "events"; vi.mock("child_proces

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/__tests__/k8s-transport.test.js

low Shell/command execution in packaging/dev tooling (dist/__tests__/ssh-transport.test.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/__tests__/ssh-transport.test.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt/ssh.js"; import * as child_process from "child_process"; import { EventEmitter } from "events"; vi.mock("child_proces

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/__tests__/ssh-transport.test.js

Tools 44

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

  • llng_download_saml_metadataingests untrusted input
  • llng_oidc_metadataingests untrusted input
  • llng_2fa_deleteno sensitive capability
  • llng_2fa_delTypeno sensitive capability
  • llng_2fa_listno sensitive capability
  • llng_config_addKeyno sensitive capability
  • llng_config_delKeyno sensitive capability
  • llng_config_exportno sensitive capability
  • llng_config_getno sensitive capability
  • llng_config_importno sensitive capability
Show 34 more tools ↓
  • llng_config_infono sensitive capability
  • llng_config_mergeno sensitive capability
  • llng_config_rollbackno sensitive capability
  • llng_config_setno sensitive capability
  • llng_config_test_emailno sensitive capability
  • llng_config_update_cacheno sensitive capability
  • llng_consent_deleteno sensitive capability
  • llng_consent_listno sensitive capability
  • llng_delete_sessionno sensitive capability
  • llng_doc_searchno sensitive capability
  • llng_import_metadatano sensitive capability
  • llng_instancesno sensitive capability
  • llng_oidc_authorizeno sensitive capability
  • llng_oidc_check_authno sensitive capability
  • llng_oidc_introspectno sensitive capability
  • llng_oidc_issuer_enableno sensitive capability
  • llng_oidc_refreshno sensitive capability
  • llng_oidc_rp_addno sensitive capability
  • llng_oidc_rp_deleteno sensitive capability
  • llng_oidc_rp_getno sensitive capability
  • llng_oidc_rp_listno sensitive capability
  • llng_oidc_tokensno sensitive capability
  • llng_oidc_userinfono sensitive capability
  • llng_oidc_whoamino sensitive capability
  • llng_purge_central_cacheno sensitive capability
  • llng_purge_local_cacheno sensitive capability
  • llng_rotate_oidc_keysno sensitive capability
  • llng_session_backupno sensitive capability
  • llng_session_deleteno sensitive capability
  • llng_session_delKeyno sensitive capability
  • llng_session_getno sensitive capability
  • llng_session_searchno sensitive capability
  • llng_session_setKeyno sensitive capability
  • llng_user_attributesno 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.0 latest A 92/100 6 1.13.0 2026-09-08

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

Use the free API → How scoring works

More in Developer Tools