Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
AynOps is a reconnaissance focused MCP Server which gives reconnaissance capabilities to AI Clients
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
ABUSEIPDB_API_KEY, HIBP_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"aynops": {
"command": "uvx",
"args": [
"AynOps"
],
"env": {
"ABUSEIPDB_API_KEY": "your-value",
"HIBP_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add aynops --env ABUSEIPDB_API_KEY=your-value --env HIBP_API_KEY=your-value -- uvx AynOps运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"aynops": {
"command": "uvx",
"args": [
"AynOps"
],
"env": {
"ABUSEIPDB_API_KEY": "your-value",
"HIBP_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"aynops": {
"type": "stdio",
"command": "uvx",
"args": [
"AynOps"
],
"env": {
"ABUSEIPDB_API_KEY": "your-value",
"HIBP_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 AynOps 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:ABUSEIPDB_API_KEY, HIBP_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.2.1)于12天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Recta
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A high-performance Model Context Protocol (MCP) server that brings real-time cybersecurity reconnaissance, attack surface mapping, and automated OSINT telemetry directly to AI agents.
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 │ └──────────────────────────┘ └──────────────────────────┘
tools/signals/) designed for direct ingestion by LLM reasoning layers.threat_analysis) for automated threat modeling workflows.AynOps is engineered from the ground up for cybersecurity engineers, red/blue teams, and security researchers seeking deterministic automation:
crt.sh append-only Merkle trees for passive subdomain and wildcard SSL discovery.v=spf1), DKIM selectors, and DMARC enforcement policies (p=reject/quarantine/none) with quantitative scoring (0–100).Server, X-Powered-By, CDN markers), Set-Cookie cookie names, tag parsing, and HTML/asset-path substring matching — returning structured detections with confidence scores (0–100) and evidence strings.Dockerfile with pre-installed Nmap and Python 3.12 for zero-dependency stdio deployment.AynOps provides 17 specialized reconnaissance tools alongside structured MCP prompt templates.
full_recon)The full_recon tool orchestrates a 3-wave concurrent pipeline designed to minimize scan latency while preserving dependency order across tools:
Target Domain
│ ├──► [Wave 1: Base Perimeter] ──► whois_lookup + dns_enumeration + ssl_inspect + email_security_check + asn_lookup │ ├──► [Wave 2: Service & Web] ──► port_scan (service) + tech_stack_detect + headers_analyzer + cert_transparency │ └──► [Wave 3: Threat Feeds] ──► ip_reputation (AbuseIPDB - dynamically bound to resolved IP address) │ ▼ Signal Aggregator (tools/signals/) ──► Unified Heuristic Security Telemetry Payload
full_recon)Documentation status: Browse the tools documentation index for all tools and their documentation availability. Detailed reference pages are currently available for tools marked Available. Tools marked Pending are implemented and included in the inventory, but their dedicated documentation pages are not yet available.
| Tool | Parameters | Underlying Mechanics / Standards | Telemetry Output | Docs |
|---|---|---|---|---|
whois_lookup | domain: str | RFC 3912 socket lookup via python-whois | Registrar metadata, registration/update/expiry timestamps, nameservers, registrant organization, and ICANN domain status codes. | Available |
dns_enumeration | domain: str | Multi-record DNS resolver (dnspython) + concurrent dictionary brute-forcing | Core Resource Records (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA), enterprise SRV records, DNSSEC records (DNSKEY, DS, RRSIG, NSEC, NSEC3), CNAME chain tracing, reverse DNS PTR lookups, and active subdomains. | Available |
| port_scan | target: str scan_type: str timeout: int | Nmap integration via python-nmap with configurable profiles | Port state (open/filtered), service banner detection (-sV), OS fingerprinting (-O), full-port scanning (-p-), and Nmap Scripting Engine vulnerability checks (--script vuln). | Available | | ssl_inspect | domain: str port: int = 443 | Direct TLS handshake & X.509 certificate parsing via cryptography | Certificate subject, issuer, serial number, validity window, days to expiration, Subject Alternative Names (SANs), negotiated cipher suite, and TLS protocol version; wildcard and self-signed detection, public key algorithm (RSA, ECDSA, Ed25519, …), TLS and cipher strength classification (Strong/Good/Weak), weak-version and weak-cipher flags, certificate status (Healthy/Expiring Soon/Expired), an overall security rating (Excellent/Good/Fair/Poor) with point-based scor
只显示了开头部分;其余内容请在仓库中阅读