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/barissozudogru/test-intel-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/barissozudogru/test-intel-mcp/test-intel)<a href="https://agentmods.dev/mcp/barissozudogru/test-intel-mcp/test-intel"><img src="https://agentmods.dev/badge/mcp/barissozudogru/test-intel-mcp/test-intel/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/barissozudogru/test-intel-mcp/test-intel"><img src="https://agentmods.dev/badge/mcp/barissozudogru/test-intel-mcp/test-intel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
test-intel 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
{
"test-intel": {
"command": "npx",
"args": [
"-y",
"@barissozudogru/test-intel-mcp"
],
"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.
- 9d ago First seen · 10 lines scan A 3f0ea005d886
test-intel is an MCP server published in the GitHub repository barissozudogru/test-intel-mcp (4 stars, last pushed 13d 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
repo-test-architect
Audit-first test strategy MCP server for repository-native test planning. Runs locally from the repo-test-architect npm package.
vacuous-tests-mcp
MCP server "vacuous-tests-mcp" as configured in zegroged/vacuous-tests-mcp. Runs locally from the vacuous-tests-mcp Python package.
mcp-devtools
MCP server "mcp-devtools" as configured in rshade/mcp-devtools-server. Launched with ./start-mcp.sh. Needs 1 environment variable to run.
waitbus
Workstation-local event bus and blocking wait/emit primitive: let any agent or script wait on or emit CI, pytest, Docker, and filesystem events without polling. GitHub Actions is source #1. Runs locally from the waitbus Python package.
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay npm package.
regex-lab-mcp
Test, explain, and generate regular expressions. Runs locally from the regex-lab-mcp npm package.