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/dev-proxy-tools/mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/dev-proxy-tools/mcp/devproxylocal)<a href="https://agentmods.dev/mcp/dev-proxy-tools/mcp/devproxylocal"><img src="https://agentmods.dev/badge/mcp/dev-proxy-tools/mcp/devproxylocal/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/dev-proxy-tools/mcp/devproxylocal"><img src="https://agentmods.dev/badge/mcp/dev-proxy-tools/mcp/devproxylocal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
DevProxyLocal 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 today.
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
{
"DevProxyLocal": {
"type": "stdio",
"command": "node",
"args": [
"${workspaceFolder}/dist/index.js"
]
}
}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.
- today First seen · 9 lines scan A 80f91523003a
DevProxyLocal is an MCP server published in the GitHub repository dev-proxy-tools/mcp (4 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-09-18.
Other mcp servers, from other repositories
xcodebuildmcp-dev
MCP server "xcodebuildmcp-dev" as configured in getsentry/XcodeBuildMCP. Runs ../../build/cli.js with node. Needs 4 environment variables to run.
XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. Runs locally from the xcodebuildmcp npm package. Needs 4 environment variables to run.
sentry
Sentry's hosted MCP server: lets the agent search and read issues, errors and traces. Remote server at mcp.sentry.dev.
mcpstub
MCP server "mcpstub" as configured in jovial-liu/mcpstub. Runs locally from the mcpstub npm package.
dtrack-mcp
Read-mostly MCP server for Dependency-Track with version lifecycle, single-call triage, duplicate-filtering ergonomics, strict input validation, broadcast triage, cross-project vulnerability search, and transient-failure retry. Runs locally from the dtrack-mcp Python package.
google-maps-geocoding-mcp
MCP server for Google Maps Geocoding API. Runs locally from the google-maps-geocoding-mcp npm package.