Lamatic MCP Server

@lamatic/mcp npm v1.0.1

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

Unified Lamatic MCP server — manage your org (dev_*), execute deployed flows (graph_*), query Lamatic docs (docs_*), and run AgentKit flows (kit_*) via AI agents.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — 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 1

medium Hardcoded egress to an external endpoint (utils/graphExecute.js)MTC-SRC-003

In the server's implementation (`utils/graphExecute.js:11`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await axios.get( `https://enterprise-api.edge.lamatic.tech/v1/organizations/${orgId}/project/${pro

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 utils/graphExecute.js

Tools 44

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

  • dev_auth_loginno sensitive capability
  • dev_check_model_statusno sensitive capability
  • dev_create_contextno sensitive capability
  • dev_create_flowno sensitive capability
  • dev_create_integration_credsno sensitive capability
  • dev_create_model_credsno sensitive capability
  • dev_create_projectno sensitive capability
  • dev_delete_contextno sensitive capability
  • dev_delete_credentialno sensitive capability
  • dev_delete_flowno sensitive capability
Show 34 more tools ↓
  • dev_delete_projectno sensitive capability
  • dev_deploy_projectno sensitive capability
  • dev_get_all_contextsno sensitive capability
  • dev_get_contextno sensitive capability
  • dev_get_cred_infono sensitive capability
  • dev_get_deploymentno sensitive capability
  • dev_get_flowsno sensitive capability
  • dev_get_oauth_urlno sensitive capability
  • dev_get_projectno sensitive capability
  • dev_list_all_deploymentsno sensitive capability
  • dev_list_all_flowsno sensitive capability
  • dev_list_integration_credsno sensitive capability
  • dev_list_model_credsno sensitive capability
  • dev_list_model_providersno sensitive capability
  • dev_list_projectsno sensitive capability
  • dev_list_supported_integrationsno sensitive capability
  • dev_rename_flowno sensitive capability
  • dev_update_credentialno sensitive capability
  • dev_update_flowno sensitive capability
  • dev_update_flow_statusno sensitive capability
  • dev_update_projectno sensitive capability
  • docs_query_docsno sensitive capability
  • graph_auth_loginno sensitive capability
  • graph_execute_flowno sensitive capability
  • graph_load_project_flowsno sensitive capability
  • graph_refresh_flowsno sensitive capability
  • kit_auth_loginno sensitive capability
  • kit_check_pr_statusno sensitive capability
  • kit_getno sensitive capability
  • kit_get_flowno sensitive capability
  • kit_listno sensitive capability
  • kit_revalidate_prno sensitive capability
  • kit_searchno sensitive capability
  • kit_validate_structureno 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
v1.0.1 latest A 95/100 1 1.13.0 2026-09-09

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

Use the free API → How scoring works

Other implementations of Lamatic 1

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

More in Developer Tools