astafford8488/agentaegis-mcp
by Various
MCP server for cybersecurity operations — compliance, vuln scans, code security, threat intel. Pay-per-use via x402.
MCP
astafford8488/agentaegis-mcp
Added 4 July 2026
Overview
An MCP server that provides cybersecurity operations including compliance checks, vulnerability scanning, code security analysis, and threat intelligence. It operates on a pay-per-use model via x402.
Best for
Best for
Developers needing on-demand cybersecurity capabilities within MCP-based agent systems
Use cases
- Integrate automated vulnerability scans into an MCP-compatible agent workflow
- Run compliance checks against infrastructure or codebases through a standardized interface
- Fetch threat intelligence data on demand for security monitoring pipelines
How to use
Install
npx -y agentaegis-mcp Tools exposed
compliance_checkvuln_scancode_securitythreat_intel
Tested with
Claude Desktop, Cursor
Example client config
{
"mcpServers": {
"agentaegis": {
"command": "npx",
"args": ["-y", "agentaegis-mcp"]
}
}
} Notes
An MCP server that provides cybersecurity operations including compliance checks, vulnerability scanning, code security analysis, and threat intelligence. It operates on a pay-per-use model via x402.
0 stars on GitHub. Last updated 2026-06-27. Licensed MIT.
Use cases
- Integrate automated vulnerability scans into an MCP-compatible agent workflow
- Run compliance checks against infrastructure or codebases through a standardized interface
- Fetch threat intelligence data on demand for security monitoring pipelines
Pros
- Covers multiple security domains in a single MCP server
- Pay-per-use pricing avoids upfront costs for low-volume usage
- Written in TypeScript for type safety and broad ecosystem compatibility
Cons
- Zero stars and no community adoption signals limited real-world testing
- Pay-per-use model may become expensive at scale compared to self-hosted alternatives
- Dependency on x402 payment infrastructure adds complexity and potential vendor lock-in
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Covers multiple security domains in a single MCP server
- Pay-per-use pricing avoids upfront costs for low-volume usage
- Written in TypeScript for type safety and broad ecosystem compatibility
Cons
- Zero stars and no community adoption signals limited real-world testing
- Pay-per-use model may become expensive at scale compared to self-hosted alternatives
- Dependency on x402 payment infrastructure adds complexity and potential vendor lock-in
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.