Lattice MCP Server

lattice-mcp npm v1.4.0

Published by aidenappl — 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 Lattice container orchestration platform

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 (verify.mjs)MTC-SRC-002

In the server's implementation (`verify.mjs:24`): 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: ecFileSync } from "node:child_process"; const failures = []; const fail = (msg) => failures.push(msg); const source =

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 verify.mjs

Tools 133

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

  • lattice_create_webhooknetwork egress
  • lattice_delete_webhooknetwork egress
  • lattice_test_webhooknetwork egress
  • lattice_update_webhooknetwork egress
  • lattice_approve_deploymentno sensitive capability
  • lattice_create_api_tokenno sensitive capability
  • lattice_create_backup_destinationno sensitive capability
  • lattice_create_containerno sensitive capability
  • lattice_create_database_instanceno sensitive capability
  • lattice_create_database_snapshotno sensitive capability
Show 123 more tools ↓
  • lattice_create_deploy_tokenno sensitive capability
  • lattice_create_env_varno sensitive capability
  • lattice_create_registryno sensitive capability
  • lattice_create_stackno sensitive capability
  • lattice_create_templateno sensitive capability
  • lattice_create_userno sensitive capability
  • lattice_create_workerno sensitive capability
  • lattice_create_worker_networkno sensitive capability
  • lattice_create_worker_tokenno sensitive capability
  • lattice_create_worker_volumeno sensitive capability
  • lattice_database_actionno sensitive capability
  • lattice_delete_api_tokenno sensitive capability
  • lattice_delete_backup_destinationno sensitive capability
  • lattice_delete_containerno sensitive capability
  • lattice_delete_database_instanceno sensitive capability
  • lattice_delete_database_snapshotno sensitive capability
  • lattice_delete_deploy_tokenno sensitive capability
  • lattice_delete_env_varno sensitive capability
  • lattice_delete_networkno sensitive capability
  • lattice_delete_registryno sensitive capability
  • lattice_delete_stackno sensitive capability
  • lattice_delete_templateno sensitive capability
  • lattice_delete_userno sensitive capability
  • lattice_delete_workerno sensitive capability
  • lattice_delete_worker_networkno sensitive capability
  • lattice_delete_worker_tokenno sensitive capability
  • lattice_delete_worker_volumeno sensitive capability
  • lattice_deploy_stackno sensitive capability
  • lattice_export_stackno sensitive capability
  • lattice_force_remove_containerno sensitive capability
  • lattice_get_anomaliesno sensitive capability
  • lattice_get_audit_logno sensitive capability
  • lattice_get_backup_destinationno sensitive capability
  • lattice_get_containerno sensitive capability
  • lattice_get_container_lifecycleno sensitive capability
  • lattice_get_container_logsno sensitive capability
  • lattice_get_container_metricsno sensitive capability
  • lattice_get_database_connectionno sensitive capability
  • lattice_get_database_credentialsno sensitive capability
  • lattice_get_database_eventsno sensitive capability
  • lattice_get_database_instanceno sensitive capability
  • lattice_get_database_lifecycle_logsno sensitive capability
  • lattice_get_database_logsno sensitive capability
  • lattice_get_deploymentno sensitive capability
  • lattice_get_deployment_logsno sensitive capability
  • lattice_get_fleet_metricsno sensitive capability
  • lattice_get_notification_prefsno sensitive capability
  • lattice_get_selfno sensitive capability
  • lattice_get_smtp_configno sensitive capability
  • lattice_get_sso_configno sensitive capability
  • lattice_get_stackno sensitive capability
  • lattice_get_stack_containersno sensitive capability
  • lattice_get_versionno sensitive capability
  • lattice_get_versionsno sensitive capability
  • lattice_get_workerno sensitive capability
  • lattice_get_worker_container_statsno sensitive capability
  • lattice_get_worker_metricsno sensitive capability
  • lattice_get_worker_port_availabilityno sensitive capability
  • lattice_healthno sensitive capability
  • lattice_import_composeno sensitive capability
  • lattice_import_stack_exportno sensitive capability
  • lattice_kill_containerno sensitive capability
  • lattice_list_all_networksno sensitive capability
  • lattice_list_api_tokensno sensitive capability
  • lattice_list_backup_destinationsno sensitive capability
  • lattice_list_containersno sensitive capability
  • lattice_list_database_instancesno sensitive capability
  • lattice_list_database_snapshotsno sensitive capability
  • lattice_list_deploy_tokensno sensitive capability
  • lattice_list_deploymentsno sensitive capability
  • lattice_list_env_varsno sensitive capability
  • lattice_list_registriesno sensitive capability
  • lattice_list_registry_repositoriesno sensitive capability
  • lattice_list_registry_tagsno sensitive capability
  • lattice_list_stacksno sensitive capability
  • lattice_list_templatesno sensitive capability
  • lattice_list_usersno sensitive capability
  • lattice_list_webhooksno sensitive capability
  • lattice_list_worker_networksno sensitive capability
  • lattice_list_worker_tokensno sensitive capability
  • lattice_list_worker_volumesno sensitive capability
  • lattice_list_workersno sensitive capability
  • lattice_open_database_consoleno sensitive capability
  • lattice_overviewno sensitive capability
  • lattice_pause_containerno sensitive capability
  • lattice_reboot_workerno sensitive capability
  • lattice_recreate_containerno sensitive capability
  • lattice_refresh_versionsno sensitive capability
  • lattice_remove_containerno sensitive capability
  • lattice_restart_containerno sensitive capability
  • lattice_restart_stackno sensitive capability
  • lattice_restore_database_snapshotno sensitive capability
  • lattice_reveal_database_credentialsno sensitive capability
  • lattice_rollback_deploymentno sensitive capability
  • lattice_save_stack_as_templateno sensitive capability
  • lattice_searchno sensitive capability
  • lattice_start_all_workerno sensitive capability
  • lattice_start_containerno sensitive capability
  • lattice_start_stackno sensitive capability
  • lattice_stop_all_workerno sensitive capability
  • lattice_stop_containerno sensitive capability
  • lattice_stop_stackno sensitive capability
  • lattice_sync_stack_composeno sensitive capability
  • lattice_test_backup_destinationno sensitive capability
  • lattice_test_registryno sensitive capability
  • lattice_test_registry_inlineno sensitive capability
  • lattice_test_smtpno sensitive capability
  • lattice_unpause_containerno sensitive capability
  • lattice_update_apino sensitive capability
  • lattice_update_backup_destinationno sensitive capability
  • lattice_update_containerno sensitive capability
  • lattice_update_database_instanceno sensitive capability
  • lattice_update_env_varno sensitive capability
  • lattice_update_notification_prefsno sensitive capability
  • lattice_update_registryno sensitive capability
  • lattice_update_smtp_configno sensitive capability
  • lattice_update_sso_configno sensitive capability
  • lattice_update_stackno sensitive capability
  • lattice_update_stack_composeno sensitive capability
  • lattice_update_userno sensitive capability
  • lattice_update_webno sensitive capability
  • lattice_update_workerno sensitive capability
  • lattice_upgrade_workerno sensitive capability

What this scan could not see

Versions 5

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
v1.4.0 latest A 93/100 1 1.13.0 2026-09-07
v1.3.0 A 93/100 1 1.12.1 2026-07-28
v1.1.1 A 96/100 0 1.10.0 2026-07-25
v1.1.0 A 96/100 0 1.9.0 2026-07-24
v1.0.1 A 100/100 0 1.5.0 2026-07-22

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

Use the free API → How scoring works

More in Productivity & Workflow