Best for
- Security teams operating under written authorization and defined rules of engagement
- Red-team researchers and security educators
- MCP users able to manage a local Node.js environment
T
T3MP3ST MCP Server
Community
A multi-agent red-teaming platform for authorized security testing.
GitHub source repository ↗
51FMRS · D
Based on the supplied README, T3MP3ST exposes one MCP tool, security_recon, as part of an offensive-security framework intended for authorized testing. No server manifest, client configuration, transport, or compatibility evidence was supplied, so those fields remain unpopulated.
T3MP3ST is an autonomous red-teaming platform and multi-agent offensive-security framework for authorized targets. Its README states that node dist/mcp-server.js exposes the security_recon tool to MCP-aware agents.
Tools
security_recon
Provides security reconnaissance capabilities; the supplied material does not specify its detailed inputs, outputs, or permission model.
Setup
From the repository root, run npm install. When working from a Git clone, run npm run build if needed. Then run node dist/mcp-server.js. The supplied material does not include a client-specific configuration example.
Fit and risk
Not for
- Targets without explicit written permission
- Users seeking unrestricted remote scanning or execution
- Users expecting fully validated end-to-end multi-agent exploitation
Required permissions
- Access to network and security-testing resources within the authorized scope
- A local Node.js environment, installed dependencies, and any configured agent or model access
- The supplied material does not specify MCP-client permissions or authentication
Risks and side effects
- This is an offensive-security tool and must be used only against owned or explicitly authorized systems
- Incorrect scoping may cause unauthorized access, data loss, or legal exposure
- The README says coordinated multi-agent exploitation remains unproven and unreliable
- External security tools and optional arsenal components may affect targets
Troubleshooting
- Confirm npm install was run from the repository root
- If using a Git clone, confirm npm run build was run when required
- Confirm the files needed by node dist/mcp-server.js exist
- Verify that the target is explicitly authorized and review scope controls
- Consult the repository's MCP Guide and related documentation for additional details
Use cases
Reconnaissance of owned or explicitly authorized targets
Red-team research, security education, and CTF support
Exposing security reconnaissance to MCP-aware agents
Supported clients
Supported clients have not been confirmed yet.