ServerSecurity & PentestOfficial

Recon MCP

Authorized-only network reconnaissance (nmap, DNS, TLS) exposed as MCP tools.

#pentest#recon#nmap#security#authorized-testing

Install

With the Zana CLI

$ zana add recon-mcp

Direct (copy-paste fallback)

$ uvx zana-recon-mcp

Environment

ZANA_SCOPE_ALLOWLIST=comma-separated hosts/CIDRs you are authorized to test

Source

catalog/servers/recon-mcp

1 files. Read them here, or pull the folder without the CLI.

Copy the folder

$ npx degit aminitech/amini-zana/catalog/servers/recon-mcp recon-mcp

No clone, no history. Just this folder.

Sparse checkout (private repos, uses your git auth)

$ git clone --depth 1 --filter=blob:none --sparse https://github.com/aminitech/amini-zana.git && cd amini-zana && git sparse-checkout set catalog/servers/recon-mcp

Single file (amini.yaml)

$ curl -sL https://raw.githubusercontent.com/aminitech/amini-zana/main/catalog/servers/recon-mcp/amini.yaml

amini.yaml

Raw

schemaVersion: 1
slug: recon-mcp
name: Recon MCP
kind: server
category: security-pentest
tags: [pentest, recon, nmap, security, authorized-testing]
summary: Authorized-only network reconnaissance (nmap, DNS, TLS) exposed as MCP tools.
description: |
  A pentest MCP server for AUTHORIZED security testing and CTF work. Wraps common
  recon primitives — port scanning, DNS enumeration, TLS inspection — behind MCP
  tools with an explicit scope-allowlist guard. Refuses targets outside the
  configured engagement scope. For defensive and authorized offensive use only.
author:
  name: Amini
  handle: amini
  url: https://amini.ai
  location:
    city: Nairobi
    country: Kenya
    countryCode: KE
runtime: python
install:
  type: uvx
  package: zana-recon-mcp
  env:
    ZANA_SCOPE_ALLOWLIST: 'comma-separated hosts/CIDRs you are authorized to test'
links:
  repo: https://github.com/zana-dev/zana
  docs: https://zana.build/servers/recon-mcp
flags:
  official: true
  verified: false

About

A pentest MCP server for AUTHORIZED security testing and CTF work. Wraps common recon primitives — port scanning, DNS enumeration, TLS inspection — behind MCP tools with an explicit scope-allowlist guard. Refuses targets outside the configured engagement scope. For defensive and authorized offensive use only.

repo docs

Author

Amini · Nairobi, Kenya