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/commitshow/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/commitshow/cli/legitshow-search)<a href="https://agentmods.dev/mcp/commitshow/cli/legitshow-search"><img src="https://agentmods.dev/badge/mcp/commitshow/cli/legitshow-search/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/commitshow/cli/legitshow-search"><img src="https://agentmods.dev/badge/mcp/commitshow/cli/legitshow-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
legitshow-search 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.
What it actually says
{
"legitshow-search": {
"command": "npx",
"args": [
"-y",
"legitshow-mcp"
],
"env": {}
}
}What else server.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 · 10 lines scan A b2c5223381c4
legitshow-search is an MCP server published in the GitHub repository commitshow/cli (1 stars, last pushed 25d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.
pseolint
Penalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest. Runs locally from the @pseolint/mcp npm package. Needs 2 environment variables to run.
centered-agent-memory
MCP server "centered-agent-memory" as configured in arlinamid/centered-agent-memory. Runs locally from the centered-agent-memory npm package.
mcp
Convert frontend folders to WordPress themes: quota, convert, status, download, preview, failures. Runs locally from the @wpconvert/mcp npm package. Needs 1 environment variable to run.
thesmos
AI-stack-agnostic repo governance: 1,137 rules, MCP server, Learning Brain, Builder Wizard, and Pantheon agents for Claude, Gemini, Cursor, Copilot, Codex, and AGENTS.md. Runs locally from the thesmos-governance npm package.
cubelife
Give AI agents a persistent pixel-art character reflecting their state in real time. Runs locally from the cubelife npm package. Needs 2 environment variables to run.