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/GNARC0TICS/ts-diagnostics-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/gnarc0tics/ts-diagnostics-mcp/ts-diagnostics-mcp)<a href="https://agentmods.dev/mcp/gnarc0tics/ts-diagnostics-mcp/ts-diagnostics-mcp"><img src="https://agentmods.dev/badge/mcp/gnarc0tics/ts-diagnostics-mcp/ts-diagnostics-mcp/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/gnarc0tics/ts-diagnostics-mcp/ts-diagnostics-mcp"><img src="https://agentmods.dev/badge/mcp/gnarc0tics/ts-diagnostics-mcp/ts-diagnostics-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ts-diagnostics-mcp 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
{ "ts-diagnostics-mcp": { "command": "npx", "args": [ "-y", "ts-diagnostics-mcp" ] } }
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 036475eb69f6
ts-diagnostics-mcp is an MCP server published in the GitHub repository GNARC0TICS/ts-diagnostics-mcp (3 stars, last pushed 12mo 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
serena
MCP server "serena" as configured in GetKlai/klai. Launched with serena start-mcp-server --context claude-code --project . --add-mode no-onboardi.
tend
Audit a JS/TS repo with established scanners, then fix the findings with parallel AI sessions in a safe scan-fix-rescan loop. Runs locally from the tend-cli npm package.
signalint
Local stdio MCP server for cached, loop-aware JS/TypeScript diagnostics (Oxlint, tsc, Biome). Runs locally from the signalint-mcp npm package.
tglider
Semantic TypeScript and JavaScript MCP server for code navigation, workspace intelligence, dependency topology, diagnostics, and refactoring. Runs locally from the tglider npm package.
lsp-intelligence
Local code intelligence for TypeScript/JavaScript — Find code, explain failures, guard API contracts, simulate changes. Runs locally from the lsp-intelligence npm package.
codebase-index
CLI tool for quick summarization of JavaScript/TypeScript codebases with symbol extraction. Runs locally from the codebase-index npm package.