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/pzalutski-pixel/javalens-mcpWrote 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/pzalutski-pixel/javalens-mcp/javalens)<a href="https://agentmods.dev/mcp/pzalutski-pixel/javalens-mcp/javalens"><img src="https://agentmods.dev/badge/mcp/pzalutski-pixel/javalens-mcp/javalens/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/pzalutski-pixel/javalens-mcp/javalens"><img src="https://agentmods.dev/badge/mcp/pzalutski-pixel/javalens-mcp/javalens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
javalens 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
{
"javalens": {
"command": "npx",
"args": [
"-y",
"javalens-mcp"
],
"env": {
"JAVA_PROJECT_PATH": "",
"JAVALENS_TIMEOUT_SECONDS": "30",
"JAVALENS_LOG_LEVEL": "INFO"
}
}
}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 · 14 lines scan A 4ed2eb3ba203
javalens is an MCP server published in the GitHub repository pzalutski-pixel/javalens-mcp (45 stars, last pushed 8d 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-30.
Other mcp servers, from other repositories
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
maven-decoder-mcp
Lets AI agents read the real source of any Maven dependency, decompiled from /.m2 or Central. Runs locally from the maven-decoder-mcp npm package. Needs 7 environment variables to run.
jvmsrc
Gradle-accurate JVM classpath; fetch Java source, signatures, and class structure for agents. Runs locally from the jvmsrc npm package. Needs 6 environment variables to run.
codex-java-lsp-mcp
MCP server "codex-java-lsp-mcp" as configured in lkyprogramer/codex-java-lsp-mcp. Runs locally from the codex-java-lsp-mcp npm package.
pyeye
MCP server "pyeye" as configured in okeefeco/pyeye-mcp. Runs locally from the ${CLAUDE_PROJECT_DIR:-.} Python package.
coderegistry
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free. Remote server at integrator.app.thecoderegistry.com.