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/agent-lsp)<a href="https://agentmods.dev/mcp/blackwell-systems/agent-lsp/agent-lsp"><img src="https://agentmods.dev/badge/mcp/blackwell-systems/agent-lsp/agent-lsp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-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 7d 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
{
"agent-lsp": {
"command": "npx",
"args": [
"-y",
"@blackwell-systems/agent-lsp"
],
"env": {}
}
}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.
- 7d ago First seen · 10 lines scan A f6292790338b
agent-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-08-30.
Other mcp servers, from other repositories
sem
Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents. Runs locally from the @ataraxy-labs/sem npm package.
gopls-mcp
gopls, the Go language server, exposed as an MCP server: lets the agent query symbols, definitions, references and diagnostics in a Go codebase. Launched with gopls mcp.
repowise
The codebase intelligence layer for your AI coding agent — dependency graph, git history, dead code, decisions, and code health, exposed over MCP. Runs locally from the repowise Python package.
trace-mcp
Framework-aware code intelligence: 81 languages, 87 frameworks, 169 tools, 40–50% fewer tokens. Runs locally from the trace-mcp npm package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Runs in Docker (ghcr.io/verivus-oss/sqry:4.8.16).
axint
Proof and repair for Apple coding agents: validate Swift, run Xcode evidence, and repair failures. Runs locally from the @axint/compiler npm package.