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/blackwell-systems/agent-lspWrote 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/blackwell-systems/agent-lsp/lsp)<a href="https://agentmods.dev/mcp/blackwell-systems/agent-lsp/lsp"><img src="https://agentmods.dev/badge/mcp/blackwell-systems/agent-lsp/lsp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
lsp 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
{
"lsp": {
"command": "agent-lsp",
"args": [
"go:gopls"
]
}
}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 · 8 lines scan A 7dfa8483eae0
lsp is an MCP server published in the GitHub repository blackwell-systems/agent-lsp (121 stars, last pushed today), 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-09-06.
Other mcp servers, from other repositories
javalens
63 semantic Java analysis tools via Eclipse JDT: navigation, refactoring, code intelligence. Runs locally from the javalens-mcp npm package. Needs 3 environment variables to run.
symbols
MCP server "symbols" as configured in Jordan-Horner/symbols. Launched with https://github.com/Jordan-Horner/symbols/releases/download/v1.0.3/syms-mcp_darwi.
nolane-habitat
MCP server "nolane-habitat" as configured in Nolane-x/Nolane-habitat. Runs locally from the nolane-habitat Python package.
swiftlens
SwiftLens is a Model Context Protocol (MCP) server that provides deep, semantic-level analysis of Swift codebases to any AI models. By integrating directly with Apple's SourceKit-LSP, SwiftLens enables AI models to understand Swift code with compiler-grade accuracy. Runs locally from the swiftlens Python package.
mache
MCP server "mache", hosted remotely at localhost, as configured in agentic-research/mache.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Runs in Docker (ghcr.io/verivus-oss/sqry:4.8.16).