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/muend/arcgis-mcp-bridgeWrote 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/muend/arcgis-mcp-bridge/arcgis-mcp-bridge)<a href="https://agentmods.dev/mcp/muend/arcgis-mcp-bridge/arcgis-mcp-bridge"><img src="https://agentmods.dev/badge/mcp/muend/arcgis-mcp-bridge/arcgis-mcp-bridge/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/muend/arcgis-mcp-bridge/arcgis-mcp-bridge"><img src="https://agentmods.dev/badge/mcp/muend/arcgis-mcp-bridge/arcgis-mcp-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
arcgis-mcp-bridge 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 12d 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
{
"arcgis-mcp-bridge": {
"command": "uvx",
"args": [
"arcgis-mcp-bridge"
],
"env": {
"ARCPY_PYTHON_PATH": "",
"ARCGIS_MCP_ALLOWED_ROOTS": "",
"ARCGIS_MCP_SCRATCH_GDB": "",
"ARCGIS_MCP_MAX_WORKERS": ""
}
}
}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.
- 12d ago First seen · 14 lines scan A 7b122fc4c01d
arcgis-mcp-bridge is an MCP server published in the GitHub repository muend/arcgis-mcp-bridge (15 stars, last pushed 1mo ago), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
arcgis
MCP server "arcgis", hosted remotely at 127.0.0.1, as configured in Knight60/ArcGIS-Pro-MCP.
arcclaude
MCP server "arcclaude" as configured in thaparSAAB14/ARCclaude. Launched with uv --directory . run arcclaude.
mcp-trustlayer
MCP server "mcp-trustlayer" as configured in neelbarm/mcp-trustlayer. Runs locally from the mcp-trustlayer Python package.
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
mcp-bash-server
MCP server "mcp-bash-server" as configured in uditk2/mcp-bash-server. Runs locally from the mcp-bash-server Python package.
wwise-mcp
MCP server "wwise-mcp" as configured in linnn-nb/wwise-mcp. Runs locally from the wwise-mcp Python package.