Labelinn MCP Server

@labelinn/mcp-server npm v2.1.0

Published by @labelinn — 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.

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

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

In the server's implementation (`dist/tools/system.js:37`): 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: isterSystemTools; const child_process_1 = require("child_process"); const os = __importStar(require("os")); const zod_1

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/tools/system.js

Tools 122

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

  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • test_webhooknetwork egress
  • update_webhooknetwork egress
  • webhook_deliveriesnetwork egress
  • webhook_eventsnetwork egress
  • add_design_elementno sensitive capability
  • add_discovered_printerno sensitive capability
  • allocate_serialsno sensitive capability
  • assign_printers_to_siteno sensitive capability
Show 112 more tools ↓
  • batch_printno sensitive capability
  • batch_verify_barcodesno sensitive capability
  • calibrate_printerno sensitive capability
  • cancel_jobno sensitive capability
  • check_usb_devicesno sensitive capability
  • clone_designno sensitive capability
  • compare_scenariosno sensitive capability
  • create_designno sensitive capability
  • create_printer_groupno sensitive capability
  • create_ruleno sensitive capability
  • create_serial_poolno sensitive capability
  • create_siteno sensitive capability
  • delete_designno sensitive capability
  • delete_design_elementno sensitive capability
  • delete_ruleno sensitive capability
  • diagnose_printerno sensitive capability
  • discover_printersno sensitive capability
  • edge_auditno sensitive capability
  • edge_discoverno sensitive capability
  • edge_fleet_healthno sensitive capability
  • edge_healthno sensitive capability
  • edge_metricsno sensitive capability
  • edge_printno sensitive capability
  • edge_printer_healthno sensitive capability
  • edge_printersno sensitive capability
  • edge_rules_cacheno sensitive capability
  • edge_rules_evaluateno sensitive capability
  • edge_verify_auditno sensitive capability
  • edge_verify_expectno sensitive capability
  • edge_verify_scanno sensitive capability
  • edge_verify_statusno sensitive capability
  • explain_errorno sensitive capability
  • factory_statusno sensitive capability
  • find_nearest_siteno sensitive capability
  • get_audit_summaryno sensitive capability
  • get_audit_trailno sensitive capability
  • get_daily_usageno sensitive capability
  • get_designno sensitive capability
  • get_design_snapshotno sensitive capability
  • get_design_variablesno sensitive capability
  • get_discovery_resultsno sensitive capability
  • get_edge_configno sensitive capability
  • get_edge_logsno sensitive capability
  • get_fleet_trendsno sensitive capability
  • get_jobno sensitive capability
  • get_predictionsno sensitive capability
  • get_printer_configno sensitive capability
  • get_printer_detailsno sensitive capability
  • get_printer_statusno sensitive capability
  • get_quality_scoreno sensitive capability
  • get_ruleno sensitive capability
  • get_scan_resultno sensitive capability
  • get_siteno sensitive capability
  • get_site_analyticsno sensitive capability
  • get_system_infono sensitive capability
  • get_usage_statsno sensitive capability
  • get_verify_job_statusno sensitive capability
  • get_verify_statsno sensitive capability
  • get_webhookno sensitive capability
  • identify_printerno sensitive capability
  • ingest_datano sensitive capability
  • list_connector_sourcesno sensitive capability
  • list_design_snapshotsno sensitive capability
  • list_designsno sensitive capability
  • list_jobsno sensitive capability
  • list_printer_groupsno sensitive capability
  • list_printersno sensitive capability
  • list_rulesno sensitive capability
  • list_serial_poolsno sensitive capability
  • list_sitesno sensitive capability
  • list_webhook_deliveriesno sensitive capability
  • list_webhook_eventsno sensitive capability
  • list_webhooksno sensitive capability
  • network_scanno sensitive capability
  • print_from_connectorno sensitive capability
  • print_imageno sensitive capability
  • print_labelno sensitive capability
  • print_zplno sensitive capability
  • publish_designno sensitive capability
  • query_verify_resultsno sensitive capability
  • render_design_previewno sensitive capability
  • render_htmlno sensitive capability
  • render_labelno sensitive capability
  • render_statusno sensitive capability
  • reprint_jobno sensitive capability
  • restart_edge_serverno sensitive capability
  • run_diagnosticsno sensitive capability
  • set_expected_barcodesno sensitive capability
  • set_printer_mediano sensitive capability
  • simulate_printno sensitive capability
  • skynet_add_noteno sensitive capability
  • skynet_end_sessionno sensitive capability
  • skynet_get_statusno sensitive capability
  • skynet_get_test_planno sensitive capability
  • skynet_record_fixno sensitive capability
  • skynet_record_restartno sensitive capability
  • skynet_run_testno sensitive capability
  • skynet_start_sessionno sensitive capability
  • submit_barcode_scanno sensitive capability
  • suggest_printerno sensitive capability
  • sync_verify_from_edgeno sensitive capability
  • system_health_checkno sensitive capability
  • test_parseno sensitive capability
  • test_printno sensitive capability
  • test_ruleno sensitive capability
  • update_designno sensitive capability
  • update_design_elementno sensitive capability
  • update_edge_configno sensitive capability
  • update_printerno sensitive capability
  • update_printer_configno sensitive capability
  • update_ruleno sensitive capability
  • void_serialsno 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
v2.1.0 latest A 93/100 1 1.10.0 2026-07-25

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

Use the free API → How scoring works

More in Developer Tools