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/pablo-albaladejo/kaiordWrote 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/pablo-albaladejo/kaiord/vitest)<a href="https://agentmods.dev/mcp/pablo-albaladejo/kaiord/vitest"><img src="https://agentmods.dev/badge/mcp/pablo-albaladejo/kaiord/vitest/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/pablo-albaladejo/kaiord/vitest"><img src="https://agentmods.dev/badge/mcp/pablo-albaladejo/kaiord/vitest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vitest 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 9d 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
{
"vitest": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@djankies/vitest-mcp"
],
"env": {}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 9d ago First seen · 11 lines scan A 6d18cba68649
vitest is an MCP server published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed yesterday), 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
hevy-coach
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
oss-autopilot
MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools. Runs locally from the @oss-autopilot/mcp npm package.
mcp-failure-lab
A chaos-engineering and resilience-testing toolkit for Model Context Protocol servers. Runs locally from the mcp-failure-lab npm package.
qai-consultant-mcp
Local, keyless MCP server: standards-grounded QA knowledge retrieval (ISTQB, OWASP, IEEE, ISO, EU AI Act), deterministic QA effort estimation, QA document quality review, and test-results health analysis. Runs locally from the qai-consultant-mcp Python package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.