AynOps logo

AynOps

Unclaimed

by AynOps

An Open Sourced Model Context Protocol (MCP) Local server that gives AI Clients real-time cybersecurity reconnaissance capabilities

Install

$docker run --rm -i aynops

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
ai-toolsclaudecybersecurity-toolsfastmcpinformation-gatheringmcp-servermodel-context-protocolpythonreconnaissancelocal-mcp-server

More in AI & ML

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

16 of 16 tools

Documented tools (16)

From project documentation. A server handshake does not verify each tool’s description or behavior.

asn_lookup

Autonomous System Number (ASN) and network ownership lookup via Team Cymru WHOIS — identifies ASN, BGP prefix, organization, registry, country, and allocation date for domains or IP addresses (no API key required)

cert_transparency

Query crt.sh Certificate Transparency logs for a domain and extract certificate, subdomain, and wildcard information

cloud_exposure_check

Checks for publicly accessible AWS S3, Azure Blob Storage, and Google Cloud Storage buckets using common bucket naming patterns derived from the target domain

cve_lookup

Search NVD for known CVEs by software name and version (no API key required)

dns_enumeration

A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, and common SRV records (SIP, LDAP, XMPP, Kerberos, Autodiscover) + common subdomain brute-forcing

email_security_check

Checks SPF, DKIM, and DMARC DNS records — returns a securityscore, rating, and actionable recommendations for missing or weak configurations

full_recon

Runs all core tools in parallel and returns combined result

headers_analyzer

Analyzes HTTP security headers — checks HSTS, CSP, X-Frame-Options, and more with severity ratings and misconfiguration details

hibp_check

Check if an email or domain appears in Have I Been Pwned breaches (HIBPAPIKEY required)

ip_reputation

Check if an IP is flagged as malicious via AbuseIPDB (api key requied)

port_scan

Nmap-powered scanner with service/version detection and security warnings

robots_txt_inspect

Fetch and parse robots.txt to reveal hidden directories and sitemaps

ssl_inspect

SSL/TLS certificate — issuer, expiry, cipher strength, SANs, TLS version

tech_stack_detect

Web server, CMS, JS frameworks, CDN, and analytics

trace_redirects

Traces the full HTTP redirect chain hop by hop — flags TLS downgrades, private-IP leaks, redirect loops, cross-domain hops, and overly long chains

whois_lookup

Domain registration data — owner, registrar, creation date, expiry, name servers

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about AynOps MCP Server

How do I connect AynOps MCP Server to Claude?
The listing records `docker run --rm -i aynops` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Cursor, VS Code as compatible clients.
Is AynOps MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can AynOps MCP Server do?
AynOps MCP Server documents 16 tools to the agent, including asn_lookup, cert_transparency, cloud_exposure_check. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.