SecPipeofficial
F
licenseA
qualityF
maintenanceEnables AI agents to orchestrate security research workflows by connecting to containerized security tools via MCP, allowing automated vulnerability analysis and pipeline execution.
24
803
mcp2agy
by uziii2208
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp2agyRun a full multi-agent security audit on ./src and generate report + fix diff"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Model Context Protocol · Multi-Agent 0day Research & Audit Pipeline
mcp2agy is an MCP-native, multi-agent security audit engine engineered for the Google Antigravity (AGY) ecosystem. It coordinates specialized subagents across the complete 0day research lifecycle: static AST taint analysis, 7-class confounder elimination, deterministic Proof-of-Concept verification (≤60s triggers), multi-chain exploit synthesis, publication-ready security reporting, and atomic code remediation.
Key Capabilities (v3.1.0 Resilient Architecture)
Strict Path Safety & Directory Containment: Validates all paths through
assertSafePath(), preventing root directory escapes, path traversal (..), and symlink attacks.Direct Object Tool Interfaces: MCP tools accept native JavaScript objects and arrays directly, eliminating JSON string escaping errors and handler parsing crashes.
Automated Run Artifacts & Compact Summaries: Saves all heavy artifacts (
candidates.json,verified_findings.json,exploit_chains.json,report.md,fixes.diff) tomcp2agy_workspace/runs/<runId>/, returning clean executive summaries to prevent LLM context explosion.Confidence-Calibrated Scanning & Noise Reduction: Categorizes candidate findings into
high,medium, andlowconfidence while automatically ignoring build/test noise (node_modules,dist,tests/,fixtures/).Strict Verifier Gating: Enforces formal reachability checks and confounder clearance before confirming findings, preventing false positives from propagating downstream.
Resilient Phase Progression: Tracks pipeline execution across 5 distinct phases with per-candidate error isolation and detailed
pipeline_state.jsonlogs.Contextual Fix Generation: Patches are generated directly from actual file code snippets and verified candidate line ranges, cross-checked with known call sites.
Related MCP server: zeroforge
Architecture & Agent Pipeline
┌────────────────────────────────────────┐
│ Master Audit Orchestrator │
│ (/audit) │
└───────────────────┬────────────────────┘
│
┌──────────────────┬─────────────────┴──────────────┬──────────────────┐
│ Phase 1: SCAN │ Phase 2: VERIFY │ Phase 2.5: CHAIN │ Phase 3: REPORT & FIX
▼ ▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Scanner │──►│ Verifier │───────────────►│ Chainer │──►│ Reporter & │
│ Subagent │ │ (Parallel) │ │ Synthesis │ │ Fixer Agents │
└──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
│ │ │ │
[Gate 1: AST] [Gate 2: PoC] [Compound CVSS] [Gate 4: Diff][+] Core Subagents & Modules
Subagent | Role Identifier | Primary Responsibility | Input | Output |
Orchestrator |
| Workflow management, gate checks, agent delegation | Target directory |
|
Scanner |
| Static AST triage, dangerous sink grep, candidate generation | Physical source files |
|
Verifier |
| 7-class confounder clearance, reachability trace, MTS PoC |
|
|
Chainer |
| Multi-primitive correlation, compound CVSS calibration |
|
|
Reporter |
| Publication-ready advisories (Mode A/B/C), root cause breakdown |
|
|
Fixer |
| 16 CWE grounded patches, multi-site call site fixes, unit tests |
|
|
Slash Commands Matrix
Command | Subsystem | Description | Example Usage |
|
| Orchestrates Scanner → Verifier → Chainer → Reporter → Fixer |
|
|
| Static 0day AST analysis producing normalized candidate records |
|
|
| Rigorous PoC verification (≤60s reproducer) & CVSS calibration |
|
|
| Composes Mode A internal reports & Mode B GHSA advisories |
|
|
| Generates minimal atomic patches ( |
|
|
| Inspects active subagents, host OS context, and workspace inventory |
|
|
| Interactive documentation hub and comprehensive tool guide |
|
|
| Concurrent OSINT, port scanning, and cloud asset mapping |
|
|
| Pwntools ROP generation, web payload weaponization |
|
|
| Static decompilation (Ghidra), dynamic Frida hooking |
|
|
| AFL++/LibFuzzer harness generation, custom scanners, Sigma rules |
|
|
| Autonomous multi-category challenge solving (pwn, rev, web, crypto) |
|
|
| Launches synchronized multi-agent offensive mesh |
|
Native MCP Tools — 15 Tools
┌──────────────────────────────────────────────────────────────────────────────────┐
│ Native MCP Tools (15 Tools) │
├──────────────────────┬──────────────────────────┬────────────────────────────────┤
│ Target Profiling │ Static Analysis │ Verification & PoC │
│ • detect_platform │ • analyze_code │ • check_reachability │
│ • profile_target │ • scan_file │ • verify_finding │
│ │ • get_patterns │ • generate_poc │
│ │ │ • calculate_cvss │
├──────────────────────┼──────────────────────────┼────────────────────────────────┤
│ Exploit Chaining │ Remediation & Fix │ End-to-End Automation │
│ • chain_findings │ • generate_fix │ • audit_pipeline │
│ • generate_report │ • check_fix_completeness │ │
│ │ • list_fix_templates │ │
└──────────────────────┴──────────────────────────┴────────────────────────────────┘Category | MCP Tools | Primary Capability |
Target Profiling |
| Detects OS environment, file hashing, and codebase topology |
Static Analysis |
| AST data-flow analysis, dangerous sink inspection & taxonomy matching |
Verification & PoC |
| 7-class confounder clearance, deterministic PoCs (≤60s), empirical CVSS |
Exploit Chaining |
| Multi-primitive exploit correlation & publication-ready advisories |
Remediation & Fix |
| 16 CWE grounded patches, multi-site call site fixes, test generation |
End-to-End |
| Automated orchestration across all pipeline phases with state persistence |
Workspace Directory Structure
All persistent outputs, candidate records, evidence bundles, and patches reside in mcp2agy_workspace/:
mcp2agy_workspace/
├── runs/
│ └── <YYYYMMDD_HHMMSS>/ ← Dedicated per-run execution directory
│ ├── pipeline_state.json ← Orchestrator state & phase progression
│ ├── candidates.json ← Scanner normalized candidates
│ ├── verified_findings.json ← Verifier confirmed findings
│ ├── exploit_chains.json ← Synthesized multi-step exploit chains
│ ├── report.md ← Reporter publication-ready markdown report
│ ├── fixes.diff ← Fixer minimal unified diff
│ ├── evidence/ ← Verifier PoCs & reachability traces
│ │ └── <CAND_ID>/
│ │ ├── reachability.md
│ │ └── mts_poc/ (poc.py, Dockerfile, run.sh)
│ └── regression_tests/ ← Fixer unit test harnesses
├── auditor_zone/
│ └── results/
│ └── <YYYYMMDD_HHMMSS>/ ← Synchronized auditor zone artifacts
├── recon/results/ ← Attack surface maps & OSINT data
├── exploits/pocs/ ← Standalone weaponized exploit scripts
├── reverse/analysis/ ← Decompiled symbols & binary call graphs
├── tools/ ← Custom scanners & fuzzing harnesses
├── ctf/solves/ ← CTF solve scripts & writeups
└── loot/ ← Discovered credentials, keys & tokensAnti-Hallucination Invariants
All subagents operate under 10 strict invariants defined in .agents/plugins/mcp2agy/rules/AGENTS.md:
# | Invariant | Description |
01 | Zero Invention | Never report a finding that static code analysis did not physically produce. |
02 | Line Count Ceiling | Never cite line ranges exceeding the physical file's total line count. |
03 | Physical Hash Echo | Every candidate record must echo the physical SHA-256 hash of the target file. |
04 | Deterministic PoC | Never mark a finding |
05 | Dual-Leg Verification | Both legs of multi-step exploit chains must be independently proven. |
06 | 7-Class Confounder Clearance | Dead code, auto-escaping, auth gates, and strict types must be formally evaluated. |
07 | Empirical CVSS | Score deductions require reproducible technical evidence — no estimation. |
08 | One-Way Information Valve | Downstream agents strictly receive normalized facts to prevent confirmation bias. |
09 | Clean Negative Results | If 0 defects exist, output |
10 | Atomic Minimal Diff | Remediation diffs must touch only vulnerable lines without introducing new TOCTOU races. |
Cross-Platform Compatibility
Node.js Lifecycle Hooks (
hooks.json): Eliminates shell script dependencies —preToolCalllogging andpostFileWritepermission hardening execute via cross-platform Node.js.Permission Hardening: Enforces
chmod 600on POSIX systems and expliciticaclspermission stripping on Windows (icacls <file> /inheritance:r /grant:r "%USERNAME%:(R,W)").Context-Aware Escaping: Distinguishes single-quote (
_pse) vs double-quote (_pde) shell string evaluation in PowerShell heredoc contexts.
Documentation
Detailed technical documentation is available in the docs/ directory:
Document | Description |
How to setup and run | |
Multi-agent orchestrator lifecycle, integrity gates & one-way information valve | |
Complete reference for all 13 slash commands and usage examples | |
Detailed input/output schemas and examples for all 15 native MCP tools | |
Cross-primitive exploit synthesis, gadget chaining & compound CVSS | |
2026+ 0day vulnerability patterns, AST grep signatures & root causes | |
Directory layout, candidate schemas, verified findings & advisory formats | |
Windows NTFS ACLs, POSIX permissions, lifecycle hooks & shell differentials |
mcp2agy · Hyperdope AI · mcp2agy_workspace/
Maintenance
–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseAqualityCmaintenanceBridges Google Antigravity CLI with MCP clients, enabling 13 specialized tools for AI-assisted coding, automation, and security audits.13
- FlicenseNot gradedqualityCmaintenanceEnables local AI agents to generate code and interact with Google Antigravity (Gemini Pro) via MCP, consuming zero API tokens.
Related MCP Connectors
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Security tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases.
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/uziii2208/mcp2agy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server