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/RonieNeubauer/cli2mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/ronieneubauer/cli2mcp/jq)<a href="https://agentmods.dev/mcp/ronieneubauer/cli2mcp/jq"><img src="https://agentmods.dev/badge/mcp/ronieneubauer/cli2mcp/jq/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/ronieneubauer/cli2mcp/jq"><img src="https://agentmods.dev/badge/mcp/ronieneubauer/cli2mcp/jq.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jq 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 1mo ago.
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.
This is a copy
73% identical to teams-mcp-dev — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"jq": {
"command": "node",
"args": [
"./dist/index.js",
"jq"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 9 lines scan A 3b93e2203ab7
jq is an MCP server published in the GitHub repository RonieNeubauer/cli2mcp (12 stars, last pushed 6mo ago), licensed MIT. 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. It is 73% identical to teams-mcp-dev, differing in 8 lines, and is treated as a copy.
Other mcp servers, from other repositories
mcptoon
MCP server "mcptoon" as configured in activeing123/mcptoon. Launched with mcptoon serve.
aiterm-mcp
Persistent terminals and one launcher for Claude, Codex, Grok, and Cursor harnesses. Runs locally from the aiterm-mcp npm package.
src-mcp
MCP server for semantic code search and codebase analysis — Treesitter parsing, AST extraction, and embedding-based indexing for any LLM that supports MCP. Runs locally from the src-mcp npm package.
file-system-mcp
MCP server "file-system-mcp" as configured in prem-thatikonda29/file-system-mcp. Runs locally from the file-system-mcp Python package.
obsidian-mcp-guard
MCP server for agent-safe Obsidian vault access with lint validation. Runs locally from the obsidian-mcp-guard Python package.
mcp-clickhouse
ClickHouse query & management for AI agents — SQL-classified read/write/destructive gating. Runs locally from the @dockndevai/mcp-clickhouse npm package. Needs 4 environment variables to run.