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/vincentvella/devloopWrote 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/vincentvella/devloop/devloop)<a href="https://agentmods.dev/mcp/vincentvella/devloop/devloop"><img src="https://agentmods.dev/badge/mcp/vincentvella/devloop/devloop/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/vincentvella/devloop/devloop"><img src="https://agentmods.dev/badge/mcp/vincentvella/devloop/devloop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
devloop 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
{
"devloop": {
"command": "npx",
"args": [
"-y",
"devloop-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.
- 1mo ago First seen · 10 lines scan A 9133357f9fe2
devloop is an MCP server published in the GitHub repository vincentvella/devloop (2 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
jshookmcp
MCP server for JavaScript analysis, security auditing, browser automation and hooks. Runs locally from the @jshookmcp/jshook npm package.
devharness
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions. Runs locally from the devharness npm package.
log-essence
Intelligent log analysis for LLMs - extract patterns, redact secrets, compress 50%+. Runs locally from the log-essence Python package.
ui-debugger-mcp
Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues. Runs locally from the @developerz.ai/ui-debugger-mcp npm package. Needs 2 environment variables to run.
feedthrough
Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser. Runs locally from the @feedthrough/mcp npm package. Needs 2 environment variables to run.
rn-devtools-hub
Drive a running React Native or Expo app from inside its JS runtime: see, act, prove. Runs locally from the rn-devtools-hub npm package.