Lexq Cli MCP Server

@lexq/cli npm v0.1.59 Source verified

Published by lexq-io — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

LexQ CLI — manage policies, simulate rules, and deploy from the terminal. Built for humans and AI agents.

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

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 2

high Read-and-egress in one tool: "lexq_webhook_subscriptions_save"MTC-FLOW-003

Tool "lexq_webhook_subscriptions_save" can both read sensitive data and send data to an external destination. Even without an explicit untrusted-input leg, this is a single-call data-exfiltration path if the model is ever manipulated.

Fix: Separate reading from sending; require explicit user confirmation before egress of file/secret contents.

Location: flow lexq_webhook_subscriptions_save

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([lexq_webhook_subscriptions_save]) and tools that can send data out ([lexq_webhook_subscriptions_get, lexq_webhook_subscriptions_save, lexq_webhook_subscriptions_delete, lexq_webhook_subscriptions_test]) are exposed together. An agent can move private data to the sink.

Evidence: sources [lexq_webhook_subscriptions_save] → sinks [lexq_webhook_subscriptions_get, lexq_webhook_subscriptions_save, lexq_webhook_subscriptions_delete, lexq_webh

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow lexq_webhook_subscriptions_save → lexq_webhook_subscriptions_get

Tools 77

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

  • lexq_webhook_subscriptions_savenetwork egressreads sensitive data
  • lexq_webhook_subscriptions_deletenetwork egress
  • lexq_webhook_subscriptions_getnetwork egress
  • lexq_webhook_subscriptions_testnetwork egress
  • lexq_ab_test_adjustno sensitive capability
  • lexq_ab_test_startno sensitive capability
  • lexq_ab_test_stopno sensitive capability
  • lexq_dataset_templateno sensitive capability
  • lexq_dataset_uploadno sensitive capability
  • lexq_deploy_deployableno sensitive capability
Show 67 more tools ↓
  • lexq_deploy_detailno sensitive capability
  • lexq_deploy_diffno sensitive capability
  • lexq_deploy_historyno sensitive capability
  • lexq_deploy_liveno sensitive capability
  • lexq_deploy_overviewno sensitive capability
  • lexq_deploy_publishno sensitive capability
  • lexq_deploy_rollbackno sensitive capability
  • lexq_deploy_scheduleno sensitive capability
  • lexq_deploy_schedulesno sensitive capability
  • lexq_deploy_undeployno sensitive capability
  • lexq_deploy_unscheduleno sensitive capability
  • lexq_domain_templates_applyno sensitive capability
  • lexq_domain_templates_listno sensitive capability
  • lexq_domain_templates_previewno sensitive capability
  • lexq_dry_runno sensitive capability
  • lexq_dry_run_compareno sensitive capability
  • lexq_facts_action_metadatano sensitive capability
  • lexq_facts_createno sensitive capability
  • lexq_facts_deleteno sensitive capability
  • lexq_facts_exportno sensitive capability
  • lexq_facts_listno sensitive capability
  • lexq_facts_unregisteredno sensitive capability
  • lexq_facts_updateno sensitive capability
  • lexq_groups_createno sensitive capability
  • lexq_groups_deleteno sensitive capability
  • lexq_groups_getno sensitive capability
  • lexq_groups_listno sensitive capability
  • lexq_groups_reorderno sensitive capability
  • lexq_groups_updateno sensitive capability
  • lexq_history_getno sensitive capability
  • lexq_history_listno sensitive capability
  • lexq_history_statsno sensitive capability
  • lexq_logs_actionno sensitive capability
  • lexq_logs_bulk_actionno sensitive capability
  • lexq_logs_getno sensitive capability
  • lexq_logs_listno sensitive capability
  • lexq_pii_reveals_listno sensitive capability
  • lexq_profile_overviewno sensitive capability
  • lexq_profile_ruleno sensitive capability
  • lexq_provenance_getno sensitive capability
  • lexq_replay_cancelno sensitive capability
  • lexq_replay_decisionno sensitive capability
  • lexq_replay_exportno sensitive capability
  • lexq_replay_listno sensitive capability
  • lexq_replay_startno sensitive capability
  • lexq_replay_statusno sensitive capability
  • lexq_requirementsno sensitive capability
  • lexq_rules_createno sensitive capability
  • lexq_rules_deleteno sensitive capability
  • lexq_rules_getno sensitive capability
  • lexq_rules_listno sensitive capability
  • lexq_rules_reorderno sensitive capability
  • lexq_rules_toggleno sensitive capability
  • lexq_rules_updateno sensitive capability
  • lexq_simulation_cancelno sensitive capability
  • lexq_simulation_exportno sensitive capability
  • lexq_simulation_listno sensitive capability
  • lexq_simulation_startno sensitive capability
  • lexq_simulation_statusno sensitive capability
  • lexq_versions_cloneno sensitive capability
  • lexq_versions_createno sensitive capability
  • lexq_versions_deleteno sensitive capability
  • lexq_versions_getno sensitive capability
  • lexq_versions_listno sensitive capability
  • lexq_versions_updateno sensitive capability
  • lexq_webhook_subscriptions_listno sensitive capability
  • lexq_whoamino sensitive capability

Toxic flows 2

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 10

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.1.59 latest A 94/100 2 1.13.0 2026-09-09
v0.1.58 A 94/100 2 1.13.0 2026-09-07
v0.1.56 A 94/100 2 1.13.0 2026-08-29
v0.1.54 A 94/100 2 1.13.0 2026-08-28
v0.1.53 A 94/100 2 1.13.0 2026-08-25
Show 5 more versions ↓
v0.1.52 A 94/100 2 1.12.1 2026-08-24
v0.1.50 A 94/100 2 1.12.1 2026-08-23
v0.1.49 A 94/100 2 1.12.1 2026-08-22
v0.1.48 A 94/100 2 1.12.1 2026-08-21
v0.1.46 A 94/100 2 1.12.1 2026-08-20

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

Use the free API → How scoring works

More in Developer Tools