Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Attack Surface MCP Server

de cyanheadsversión 0.5.0i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.cyanheads/attack-surface-mcp-server

Instalar

Resumen

Descripción del creador (original en inglés)

Passive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio, Streamable HTTP
  • Categoría: Otros
  • Debes completar: SHODAN_API_KEY, CERTSPOTTER_API_KEY

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
  • Debes completar tú: SHODAN_API_KEY, CERTSPOTTER_API_KEY, ATTACKSURFACE_DEFAULT_RESOLVERS, ATTACKSURFACE_HTTP_USER_AGENT, ATTACKSURFACE_MAX_SUBDOMAINS, ATTACKSURFACE_RDAP_BOOTSTRAP_URL, ATTACKSURFACE_ALLOW_PRIVATE_TARGETS, MCP_LOG_LEVEL

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

  • npmNode.js instalado (para el comando npx)

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "attack-surface": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/attack-surface-mcp-server"
      ],
      "env": {
        "SHODAN_API_KEY": "your-value",
        "CERTSPOTTER_API_KEY": "your-value",
        "ATTACKSURFACE_DEFAULT_RESOLVERS": "your-value",
        "ATTACKSURFACE_HTTP_USER_AGENT": "your-value",
        "ATTACKSURFACE_MAX_SUBDOMAINS": "your-value",
        "ATTACKSURFACE_RDAP_BOOTSTRAP_URL": "your-value",
        "ATTACKSURFACE_ALLOW_PRIVATE_TARGETS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add attack-surface --env SHODAN_API_KEY=your-value --env CERTSPOTTER_API_KEY=your-value --env ATTACKSURFACE_DEFAULT_RESOLVERS=your-value --env ATTACKSURFACE_HTTP_USER_AGENT=your-value --env ATTACKSURFACE_MAX_SUBDOMAINS=your-value --env ATTACKSURFACE_RDAP_BOOTSTRAP_URL=your-value --env ATTACKSURFACE_ALLOW_PRIVATE_TARGETS=your-value --env MCP_LOG_LEVEL=your-value -- npx -y @cyanheads/attack-surface-mcp-server

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "attack-surface": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/attack-surface-mcp-server"
      ],
      "env": {
        "SHODAN_API_KEY": "your-value",
        "CERTSPOTTER_API_KEY": "your-value",
        "ATTACKSURFACE_DEFAULT_RESOLVERS": "your-value",
        "ATTACKSURFACE_HTTP_USER_AGENT": "your-value",
        "ATTACKSURFACE_MAX_SUBDOMAINS": "your-value",
        "ATTACKSURFACE_RDAP_BOOTSTRAP_URL": "your-value",
        "ATTACKSURFACE_ALLOW_PRIVATE_TARGETS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "attack-surface": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/attack-surface-mcp-server"
      ],
      "env": {
        "SHODAN_API_KEY": "your-value",
        "CERTSPOTTER_API_KEY": "your-value",
        "ATTACKSURFACE_DEFAULT_RESOLVERS": "your-value",
        "ATTACKSURFACE_HTTP_USER_AGENT": "your-value",
        "ATTACKSURFACE_MAX_SUBDOMAINS": "your-value",
        "ATTACKSURFACE_RDAP_BOOTSTRAP_URL": "your-value",
        "ATTACKSURFACE_ALLOW_PRIVATE_TARGETS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • SHODAN_API_KEY secreto env
    Optional Shodan API key. Enables attacksurface_lookup_host; absent → that one tool returns source_unavailable and the rest of the server works.
  • CERTSPOTTER_API_KEY secreto env
    Optional Certspotter API key. Raises CT-fallback rate limits; absent → free unauthenticated tier.
  • ATTACKSURFACE_DEFAULT_RESOLVERS env
    Comma-separated default DNS resolver IPs for attacksurface_resolve_dns.
  • ATTACKSURFACE_HTTP_USER_AGENT env
    Default User-Agent for attacksurface_probe_http (overridable per call).
  • ATTACKSURFACE_MAX_SUBDOMAINS env
    Map/snapshot resolution cap; enumeration also caps each page at 50 candidates.
  • ATTACKSURFACE_RDAP_BOOTSTRAP_URL env
    RDAP bootstrap base URL; override for a private/mirrored RDAP.
  • ATTACKSURFACE_ALLOW_PRIVATE_TARGETS env
    Set true to permit non-public target ranges for trusted internal-network assessment; URL and HTTP(S) scheme checks remain enforced.
  • MCP_LOG_LEVEL env
    Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub cyanheads, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 32505 servidores de esta categoría
  • Publicado en el registro más recientemente que el 82% de los otros 32505 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 32505 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Attack Surface MCP Server?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: SHODAN_API_KEY, CERTSPOTTER_API_KEY

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.5.0) llegó al registro hace 7 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, topo^alpin

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar

Remote Desktop Commander

de desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Se ejecuta en la nube★ 211Actualizado ayer
Instalar

topo^alpin

de topoalpin.app

Avalanche bulletins and mountain weather forecasts for any place in the Alps.

Se ejecuta en la nubeActualizado hoy
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

@cyanheads/attack-surface-mcp-server Passive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan via MCP. STDIO or Streamable HTTP. 8 Tools • 1 Resource


[!IMPORTANT]

Authorized, defensive use only. Point this server only at assets you own or are explicitly authorized to assess. It performs passive, non-intrusive reconnaissance — it reads public records (Certificate Transparency logs, DNS, RDAP/WHOIS) and each target's *own* published surface (one TLS handshake and one HTTP GET per host). It does not port-scan, exploit, brute-force, fuzz, or probe for vulnerabilities; that capability is excluded from the surface by design, not gated behind a flag. Output is descriptive — what exists and what the security posture is — never an exploitation plan. Every outbound connection passes an SSRF guard that refuses private, loopback, link-local, and cloud-metadata targets.


Overview

Passive external attack-surface mapping (EASM) over Certificate Transparency logs, DNS, TLS, HTTP, and RDAP/WHOIS registries, with optional Shodan host intelligence. Discover subdomains, resolve DNS records, and inspect TLS and HTTP security posture across a domain's live hosts.

The attack-surface guide covers assessment coverage and evidence-preserving triage. It ships with plugin, npm, MCPB and Docker distributions and is served through the MCP Skills extension for supporting clients.

Tools
ToolDescription
attacksurface_map_domainFlagship workflow. Maps a domain's external surface end to end: CT-log subdomain discovery → DNS liveness → (standard+) DNS records, TLS posture, HTTP headers/tech → optional RDAP/WHOIS → (thorough + key) per-IP Shodan enrichment. Returns a structured surface map and a defensive assessment of observable facts.
attacksurface_enumerate_subdomainsPassive subdomain discovery from Certificate Transparency logs (crt.sh → Certspotter → TLS-SAN fallback chain), with DNS resolution to mark which names are live. Per-source provenance; no DNS brute-forcing.
attacksurface_resolve_dnsResolve and enumerate DNS records (A/AAAA/CNAME/MX/NS/TXT/CAA) for one or more hosts across multiple public resolvers, with optional reverse DNS (PTR). Per-resolver values surface propagation gaps.
attacksurface_inspect_tlsInspect TLS/SSL posture via a real read-only handshake: protocol, cipher, leaf certificate and chain depth, SANs, validity window, days-to-expiry, issuer, validation status. Reports invalid/expired/self-signed certs instead of failing.
attacksurface_probe_httpPassive HTTP(S) probe: one GET following redirects. Returns status, redirect chain, headers, a security-header audit (HSTS/CSP/X-Frame-Options/cookie flags/CORS reflection), and an evidence-bound technology fingerprint.
attacksurface_lookup_registrationRegistration and ownership lookup via RDAP (JSON; WHOIS fallback). A domain returns registrar, status, lifecycle events, nameservers, DNSSEC; an IP/CIDR returns netblock, allocation CIDRs, origin ASN, country.
attacksurface_lookup_hostInfrastructure intelligence for a single IP (open ports, banners, software versions, ASN, geo) or a faceted internet-wide search, via Shodan. Requires `SHODAN_API_KEY` — returns a typed source_unavailable error when unset; the rest of the server is unaffected.
attacksurface_recon_guidanceOffline defensive review with topic selection, bounded priority/suggestion pages, local follow-up calls and product/version advisory-check guidance. No external calls.
Resources
ResourceDescription
attacksurface://surface/{domain}Read-once snapshot of a domain's mapped external surface (subdomains, live hosts, per-host DNS/TLS/HTTP posture summary), with separate candidate and 50-host detail coverage.

All resource data is also reachable via tools — tool-only clients lose nothing, since attacksurface_map_domain covers the same ground.

Capability reference

attacksurface_map_domain tool
  • depth: quick discovers subdomains and liveness; standard adds DNS records, TLS, and HTTP posture; thorough adds per-IP Shodan data when a key is present, otherwise a note.
  • Returns a structured surface map and a defensive assessment of observable facts. Failed sources and unreachable hosts become notes, and subdomain resolution is capped by ATTACKSURFACE_MAX_SUBDOMAINS (default 200), with truncation disclosed.
  • includeRegistration adds RDAP/WHOIS data for the apex at standard or thorough depth. Standard and thorough also return DNS records from the first configured resolver plus propagation mismatches for live hosts; null posture at quick depth means the work was skipped.
  • coverage lists what was left unexamined or without host detail (unexamined, detailOmitted), and retrieval gives up to three ready-to-run follow-up calls (DNS/TLS batches of at most 50 hosts, one HTTP URL). nextToolSuggestions prefills an attacksurface_recon_guidance call for up to 50 hosts, with guidanceCoverage naming any omitted.

attacksurface_enumerate_subdomains tool
  • Discovers names through crt.sh → Certspotter → the apex TLS certificate SANs, then resolves DNS liveness. includeUnresolved: false keeps only live hosts; filteredAddressErrors retains DNS failures for excluded names.
  • Returns each name's source provenance and per-source status. complete, pagesFetched, and incompleteReason disclose partial coverage, and addressError separates DNS failures from ENODATA/ENOTFOUND absence.
  • offset and limit (default 50, larger requests clamped) page through candidates, bounded by min(50, ATTACKSURFACE_MAX_SUBDOMAINS). Use nextOffset or the prefilled continuation for the next page, and remainingCount to see what is left. CT logs are re-read per page, so changes can shift offsets.

attacksurface_resolve_dns tool
  • Accepts 1–1000 hosts and processes the first 50 in input order; processedCount and remainingHosts show what to resubmit. Queries A, AAAA, CNAME, MX, NS, TXT, and CAA across public resolvers (default 8.8.8.8, 1.1.1.1, 9.9.9.9); reverse DNS (PTR) is optional.
  • Returns per-resolver answers to expose propagation gaps, with canonical records from the first configured resolver. Resolver failures (including SERVFAIL) appear in queryError and hostError next to any successful records.
  • Private or loopback resolver IPs produce blocked_resolver; an individual host failure becomes a per-host error.

attacksurface_inspect_tls tool
  • Accepts 1–1000 hosts and processes the first 50 in input order; processedCount and remainingHosts show what to resubmit. Port defaults to 443 and handshake timeout to 8000ms (1000–30000ms).
  • Returns negotiated protocol, cipher, leaf certificate and chain depth, SANs, issuer, validity window, days to expiry, and validation status. Invalid, expired, and self-signed certificates are reported; one host failure becomes a per-host error.
  • Chain trust (validationAuthorized/validationError) and hostname match (identityAuthorized/identityError) are separate checks. daysUntilExpiry is null only when the expiry date cannot be parsed.

attacksurface_probe_http tool
  • Accepts one HTTP(S) URL; timeout defaults to 10000ms (1000–30000ms) and covers the whole probe. Follows up to ten redirects with an SSRF check at every hop; a refused target produces blocked_target, and exceeding the redirect limit returns finalStatus: 0 and a transportError.
  • Returns status, redirect chain, raw headers, security-header findings (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, cookie flags, CORS reflection), and technology detections with their triggering evidence. CSP analysis covers frame-ancestors only.
  • bodyInspection reports complete, limited (64,000-byte prefix cap), failed, or not_read; a body failure keeps the status and headers.

attacksurface_lookup_registration tool
  • Accepts a domain, IP, or CIDR (prefix IPv4 0–32, IPv6 0–128); type (auto / domain / ip) controls interpretation. Uses RDAP first, then WHOIS when needed.
  • Domain results include registrar, EPP statuses, lifecycle events, nameservers, and DNSSEC; IP/CIDR results include netblock, allocation CIDRs, ASN, and country. Sparse or redacted fields stay unknown, and the raw WHOIS response is kept in rawWhois.
  • An explicit WHOIS no-match returns no_match; a failed referral or an empty or unrecognized WHOIS response returns source_unavailable.

attacksurface_lookup_host tool
  • mode: "host" (default) looks up one bare IPv4/IPv6 address and returns invalid_target for anything else; mode: "search" takes an internet-wide query with optional facets and may consume Shodan query credits. Requires SHODAN_API_KEY.
  • Search returns one 100-match page per call (page defaults to 1, ignored in host mode), with hasMore, nextPage, and a prefilled continuation. Later pages are opt-in and may consume credits.
  • Returns ports, banners, software versions, hostnames, ASN, and geography from Shodan's last scan. Missing credentials produce source_unavailable; no host data produces no_data. The server performs no port scans.

attacksurface_recon_guidance tool
  • Takes prior findings (hosts, certificates, missing headers, software versions, ports). Topic triage covers all findings ordered by urgency, posture covers TLS/header hardening, and coverage covers inspection and version gaps. Open ports are inventory evidence, never proof of a vulnerability.
  • Returns priorities plus suggestions as {toolName, reason, args} that ta

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx