MLNops
MLNops is a local-first MCP server for authorized infrastructure reconnaissance and security posture analysis. It provides DNS, WHOIS, SSL/TLS, subdomain, ASN, cloud exposure, and full-recon tools for MCP clients.
README
<div align="center"> <img src=".github/images/logo.svg" alt="MLNops — Monitor, Link, Navigate" width="100%">
<p><strong>Local-first cyber reconnaissance for MCP clients.</strong></p> <p>Monitor the surface. Link the evidence. Navigate the risk.</p>
What is MLNops?
MLNops is a Python MCP server that equips AI clients with live infrastructure reconnaissance tools. It combines domain registration, DNS, TLS, network, web, email-security, certificate-transparency, and reputation evidence into one structured workflow.
MLNops does not replace professional judgment. It collects evidence and exposes it through MCP; the connected AI client decides which tool to invoke and how to explain the result.
operator request
│
▼
MCP client ──► MLNops tool registry
│
┌─────────┼─────────┐
▼ ▼ ▼
passive active external
records probes intelligence
└─────────┼─────────┘
▼
normalized signals
▼
correlated threat report
MLNops runs locally, but reconnaissance still creates outbound traffic to target systems and third-party services. Use it only on assets you own or are explicitly authorized to assess.
Capability matrix
Full reconnaissance pipeline
full_recon executes dependency-aware waves and returns raw evidence, tool coverage, normalized signals, and a prompt-ready summary.
| Signal | What MLNops inspects |
|---|---|
| Ownership | WHOIS registration, expiry, registrar, and name servers |
| DNS | A, AAAA, MX, NS, TXT, CNAME, SOA, and common subdomains |
| TLS | Certificate chain, issuer, SANs, cipher, protocol, and expiry |
| SPF, DKIM, DMARC, score, and remediation guidance | |
| Network | ASN, BGP prefix, country, registry, and network organization |
| Exposure | Nmap ports, services, and detected versions |
| Web stack | Server, CMS, frameworks, CDN, analytics, and header posture |
| Discovery | Certificate Transparency subdomains with passive-DNS fallback |
| Reputation | AbuseIPDB confidence and malicious-IP indicators |
Focused tools
| Tool | Purpose |
|---|---|
headers_analyzer |
Detailed HTTP security-header analysis |
cve_lookup |
NVD CVE search by software and version |
cloud_exposure_check |
Checks likely public S3, Azure Blob, and GCS names |
trace_redirects |
Maps redirect chains and flags downgrade, loop, and private-IP risks |
robots_txt_inspect |
Parses directives, paths, crawl delays, hosts, and sitemaps |
MCP prompt
threat_analysis turns full_recon signals into a structured report with:
- an executive security posture;
- confirmed and likely findings separated by severity;
- a transparent 100-point risk score;
- an immediate, weekly, and monthly remediation roadmap;
- explicit insufficient-data handling when a tool is blocked or fails.
Quick start
Requirements
- Python 3.12+
- uv
- Nmap for port scanning
- An MCP-capable client such as Claude Desktop, Cursor, or VS Code
Install
git clone https://github.com/Milindu-Weerawarna/MLNops.git
cd MLNops
uv sync --locked
Confirm Nmap is available:
nmap --version
Connect an MCP client
Use absolute paths in your client configuration.
Windows
{
"mcpServers": {
"MLNops": {
"command": "C:\\full\\path\\to\\MLNops\\.venv\\Scripts\\python.exe",
"args": ["C:\\full\\path\\to\\MLNops\\server.py"],
"env": {
"ABUSEIPDB_API_KEY": "optional-key"
}
}
}
}
macOS / Linux
{
"mcpServers": {
"MLNops": {
"command": "/full/path/to/MLNops/.venv/bin/python",
"args": ["/full/path/to/MLNops/server.py"],
"env": {
"ABUSEIPDB_API_KEY": "optional-key"
}
}
}
}
ABUSEIPDB_API_KEY is optional and used only by ip_reputation. All other tools work without it.
Restart the MCP client after changing its configuration, then ask:
What MLNops security tools are available?
Operator examples
Run DNS enumeration on example.com.
Inspect the TLS posture of example.com.
Scan scanme.nmap.org with service detection.
Look up CVEs for Apache 2.4.49.
Trace redirects for https://example.com.
Run a complete authorized recon on my-domain.example.
For a correlated report, attach the threat_analysis MCP prompt and invoke full_recon.
Port-scan profiles
| Profile | Nmap behavior | Typical use |
|---|---|---|
basic |
Fast scan of common ports | Rapid exposure check |
service |
Common ports plus version detection | Default full-recon profile |
os |
OS detection; elevated privileges may be required | Host characterization |
full |
All 65,535 TCP ports | Deep authorized assessment |
vuln |
Nmap vulnerability scripts on common ports | Focused validation |
Architecture
server.py MCP entry point and tool registration
tools/ Reconnaissance implementations
tools/signals/ Evidence normalization and warning extraction
tools/prompts/ Correlation prompt templates
utils/ Shared validation and parsing helpers
tests/ Unit and regression tests
mcp.json / server.json MCP distribution metadata
The full-recon scheduler runs tools in waves:
- Lightweight identity and configuration checks.
- Active service inspection and passive discovery.
- Reputation analysis after an IP address has been resolved.
A failed tool is recorded as failed or skipped without terminating the remaining scan.
Development
uv sync --locked
uv run pytest tests -q
Run the MCP development inspector:
uv run fastmcp dev inspector server.py
See contributing.md for tool contracts, signal extraction, testing, and registration guidance.
Responsible use
- Scan only systems you own or have explicit written permission to test.
- Use
scanme.nmap.orgwhen learning Nmap against a public target. - Treat heuristic findings as leads that require validation.
- Do not interpret a missing response as proof of a vulnerability.
- Follow the laws and organizational policies that apply to your environment.
License and lineage
MLNops is an independent fork and rebuild based on AynOps. It is distributed under the MIT License. The original copyright notice is retained in LICENSE, and subsequent MLNops modifications are identified there as well.
Maintained by Milindu Weerawarna.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。