by Juniper · MCP Server · ★ 103
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
git clone https://github.com/Juniper/junos-mcp-server.git
Taken from the project's README on GitHub. Check the security audit before running it.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 103 |
| Forks | 52 |
| Language | Python |
| Category | MCP Server |
| License | Apache-2.0 |
| Quality Score | 71/100 |
| Open Issues | 4 |
| Last Updated | 2026-08-15 |
| Created | 2025-06-11 |
| Platforms | claude-code, cli, mcp, python |
| Est. Tokens | ~21k |
junos-mcp-server A Model Context Protocol (MCP) server for Juniper Junos devices that enables LLM interactions with network equipment. Table of Contents junos-mcp-server Table of Contents Important Security Notice Security Requirements Security Best Practices Important Configuration Notice Getting Started Running with uv Start Junos MCP Server Configuration Config for Claude Desktop (stdio...
These tools work well together with junos-mcp-server for enhanced workflows:
Explore other popular mcp server tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: