Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lexq-io/lexq-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lexq-io/lexq-cli/lexq)<a href="https://agentmods.dev/mcp/lexq-io/lexq-cli/lexq"><img src="https://agentmods.dev/badge/mcp/lexq-io/lexq-cli/lexq/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lexq-io/lexq-cli/lexq"><img src="https://agentmods.dev/badge/mcp/lexq-io/lexq-cli/lexq.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lexq scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"lexq": {
"command": "npx",
"args": [
"-y",
"@lexq/cli",
"-y"
],
"env": {
"LEXQ_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 13 lines scan A 22af1f4cc8bd
lexq is an MCP server published in the GitHub repository lexq-io/lexq-cli (0 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other mcp servers, from other repositories
pipefy
MCP server "pipefy", hosted remotely at mcp.pipefy.com, as configured in pipefy/ai-toolkit.
backlog
MCP server "backlog" as configured in jvgomg/podkit. Launched with mise exec -- backlog mcp start.
crmy
CRMy CLI — Local CLI + stdio MCP server. Runs locally from the @crmy/cli npm package.
buggazi
Project management for coding agents. Bugs, features, sprints. 71 tools, stdio or remote SSE. Runs locally from the buggazi npm package. Needs 1 environment variable to run.
github
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.