A
AynOps/AynOps
Live reconnaissance and attack-surface mapping for agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Install command from the repository
brew install nmap
Parsed from the README we fetched on 2026-11-07; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
brew install nmap
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
brew install nmap. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
A high-performance Model Context Protocol (MCP) server that brings real-time cyb
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
## 📚 Table of Contents
Overview
Features
Tools & Prompts
Demo
Prerequisites
Installation
Usage
Examples
Registries & Ecosystem
LLM Client Behavior & Security Considerations
Legal & Ethical Usage
Known Limitations
Project Structure
Roadmap & Discussions
Contributing
License
Author
## 🌐 Overview
Modern Large Language Models (LLMs) operate in sandboxed, non-deterministic execution environments devoid of native raw-socket access, packet crafting abilities, and live network reconnaissance primitives. When tasked with auditing an attack surface, AI agents are fundamentally constrained by static training cutoff boundaries and an inability to query live network interfaces.
AynOps bridges this operational divide. Built on top of the Model Context Protocol (MCP) specification using the FastMCP framework, AynOps exposes an extensible suite of deterministic cybersecurity reconnaissance tools directly to LLM agents (such as Cursor, VS Code, Claude Desktop, and custom MCP clients) over a standard JSON-RPC 2.0 stdio transport.
┌───────────────────────────┐ JSON-RPC 2.0 (stdio) ┌────────────────────────────────────────────────────────┐
│ AI / LLM Client │ ◄──────────────────────────────────► │ AynOps MCP Server │
│ (Cursor, VS Code, Claude) │ │ (Local Daemon) │
└───────────────────────────┘ └──────────────────────────┬─────────────────────────────┘
┌───────────────────────────────────────────────────────────┴──────────────────────────────┐
▼ ▼ ▼
┌──────────────────────────┐ ┌──────────────────────────┐ ┌──────────────────────────┐
│ Active Network │ │ DNS & OSINT │ │ Web & Cloud Audits │
│ • Nmap Port Scanner │ │ • Authoritative WHOIS │ │ • SSL/TLS X.509 Parser │
│ • Team Cymru ASN BGP │ │ • dnspython Resolver │ │ • HTTP Headers Linting │
│ • AbuseIPDB Threat Intel│ │ • crt.sh CT Log Parser │ │ • Multi-Cloud Storage │
└──────────────────────────┘ │ • Subdomain Takeover │ │ • Redirect Hop Tracer │
└──────────────────────────┘ └──────────────────────────┘
### Architectural Highlights
🔒 Local-First & Zero-Telemetry Egress: AynOps runs entirely as a local daemon on your host or isolated container. Target queries, raw IP telemetry, and internal host details never transit through external telemetry collectors.
⚡ Wave-Based Concurrent Pipeline: Orchestrates complex reconnaissance tasks through an intelligent 3-wave async execution model, resolving foundational network primitives in parallel before dispatching dependent service, web, and threat intelligence probes.
🧠 Unified Heuristic Signal Extraction: Raw outputs from heterogeneous utilities (Nmap, dnspython, cryptography, socket APIs) are parsed and normalized into structured threat signals (tools/signals/) designed for direct ingestion by LLM reasoning layers.
🛠️ Standardized MCP Tool & Prompt Primitives: Fully compliant with the official Model Context Protocol standard, packaging ready-to-use tool declarations and meta-prompts (threat_analysis) for automated threat modeling workflows.
## ⚡ Features
AynOps is engineered from the ground up for cybersecurity engineers, red/blue teams, and security researchers seeking deterministic automation:
🔒 100% Local-First Execution: Self-hosted local daemon with zero telemetry leaks, preserving target confidentiality.
Overview
Features
Tools & Prompts
Demo
Prerequisites
Installation
Usage
Examples
Registries & Ecosystem
LLM Client Behavior & Security Considerations
Legal & Ethical Usage
Known Limitations
Project Structure
Roadmap & Discussions
Contributing
License
Author
## 🌐 Overview
Modern Large Language Models (LLMs) operate in sandboxed, non-deterministic execution environments devoid of native raw-socket access, packet crafting abilities, and live network reconnaissance primitives. When tasked with auditing an attack surface, AI agents are fundamentally constrained by static training cutoff boundaries and an inability to query live network interfaces.
AynOps bridges this operational divide. Built on top of the Model Context Protocol (MCP) specification using the FastMCP framework, AynOps exposes an extensible suite of deterministic cybersecurity reconnaissance tools directly to LLM agents (such as Cursor, VS Code, Claude Desktop, and custom MCP clients) over a standard JSON-RPC 2.0 stdio transport.
┌───────────────────────────┐ JSON-RPC 2.0 (stdio) ┌────────────────────────────────────────────────────────┐
│ AI / LLM Client │ ◄──────────────────────────────────► │ AynOps MCP Server │
│ (Cursor, VS Code, Claude) │ │ (Local Daemon) │
└───────────────────────────┘ └──────────────────────────┬─────────────────────────────┘
┌───────────────────────────────────────────────────────────┴──────────────────────────────┐
▼ ▼ ▼
┌──────────────────────────┐ ┌──────────────────────────┐ ┌──────────────────────────┐
│ Active Network │ │ DNS & OSINT │ │ Web & Cloud Audits │
│ • Nmap Port Scanner │ │ • Authoritative WHOIS │ │ • SSL/TLS X.509 Parser │
│ • Team Cymru ASN BGP │ │ • dnspython Resolver │ │ • HTTP Headers Linting │
│ • AbuseIPDB Threat Intel│ │ • crt.sh CT Log Parser │ │ • Multi-Cloud Storage │
└──────────────────────────┘ │ • Subdomain Takeover │ │ • Redirect Hop Tracer │
└──────────────────────────┘ └──────────────────────────┘
### Architectural Highlights
🔒 Local-First & Zero-Telemetry Egress: AynOps runs entirely as a local daemon on your host or isolated container. Target queries, raw IP telemetry, and internal host details never transit through external telemetry collectors.
⚡ Wave-Based Concurrent Pipeline: Orchestrates complex reconnaissance tasks through an intelligent 3-wave async execution model, resolving foundational network primitives in parallel before dispatching dependent service, web, and threat intelligence probes.
🧠 Unified Heuristic Signal Extraction: Raw outputs from heterogeneous utilities (Nmap, dnspython, cryptography, socket APIs) are parsed and normalized into structured threat signals (tools/signals/) designed for direct ingestion by LLM reasoning layers.
🛠️ Standardized MCP Tool & Prompt Primitives: Fully compliant with the official Model Context Protocol standard, packaging ready-to-use tool declarations and meta-prompts (threat_analysis) for automated threat modeling workflows.
## ⚡ Features
AynOps is engineered from the ground up for cybersecurity engineers, red/blue teams, and security researchers seeking deterministic automation:
🔒 100% Local-First Execution: Self-hosted local daemon with zero telemetry leaks, preserving target confidentiality.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/aynops-aynops/)
- Source
- awesome · https://github.com/AynOps/AynOps
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.