# Recon

> Public-metadata domain intelligence from DNS, certificate transparency, and unauthenticated identity discovery. Local Python CLI, versioned JSON, and stdio MCP server. No credentials or active scanning.

- **Type:** MCP server
- **Install:** `agentstack add mcp-blisspixel-recon`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [blisspixel](https://agentstack.voostack.com/s/blisspixel)
- **Installs:** 0
- **Category:** [Communication](https://agentstack.voostack.com/c/communication)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [blisspixel](https://github.com/blisspixel)
- **Source:** https://github.com/blisspixel/recon
- **Website:** https://pypi.org/project/recon-tool/

## Install

```sh
agentstack add mcp-blisspixel-recon
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# recon

[](https://github.com/blisspixel/recon/actions/workflows/ci.yml)
[](https://pypi.org/project/recon-tool/)
[](https://pypi.org/project/recon-tool/)
[](https://github.com/blisspixel/recon/blob/main/LICENSE)
[](https://scorecard.dev/viewer/?uri=github.com/blisspixel/recon)

Passive domain intelligence from public sources. recon reads public DNS,
certificate transparency, and unauthenticated Microsoft and Google identity
discovery endpoints to compose typed observations around a domain's public
technology and identity namespace. A domain is the query coordinate, not proof
of one organization, owner, account, or deployed product.

It uses no credentials, no API keys, no paid feeds, and no active scanning. It
ships as a local Python package with a CLI, versioned JSON output, and a stdio
MCP server.
It is not a hosted service, scheduler, vulnerability scanner, company research
tool, or firmographic database.

> **Defensive use only.** Use recon for legitimate posture review, IT
> architecture review, vendor diligence, and defensive hardening. See
> [docs/legal.md](https://github.com/blisspixel/recon/blob/main/docs/legal.md) for the intended-use policy.

## Quick Start

Install with `uv` or `pipx`:

```bash
uv tool install recon-tool
# or
pipx install recon-tool
```

Python 3.11 through 3.14 is supported. The latest Python 3.14 patch is
recommended for new installations and development; older supported versions
retain the same product behavior and output contracts. Current measurements
and version-specific decisions are in
[docs/performance.md](https://github.com/blisspixel/recon/blob/main/docs/performance.md).

Optional helpers at `scripts/install.ps1` and `scripts/install.sh` use an
existing `uv` or `pipx` installation. Download a
[release-tag source archive](https://github.com/blisspixel/recon/releases/latest),
review the local helper, and then run it. Each helper installs the exact version
represented by that tag, preserves a sole existing `uv` or `pipx` owner, and
refuses ambiguous or unmanaged installations. Review the helper from a newer
tag before using it to update. Do not pipe mutable branch content directly into
a shell.

For a provenance-first path that verifies the exact GitHub and PyPI artifacts,
their signed evidence, and their byte parity before optional installation, use
the [cross-platform consumer verification recipe](https://github.com/blisspixel/recon/blob/main/docs/supply-chain.md#consumer-verification-quick-path).
The release workflow in this source revision signs the completed SBOM with the
distributions and validates any existing release's exact identity and
expected-only inventory before replacing assets during recovery. The published
v2.6.3 bundle predates the SBOM subject expansion; the quick path binds that
single historical exception to its exact commit and still validates the SBOM.

Open a new terminal and run an offline verification of the installed command:

```bash
recon --version
```

Optionally test online connectivity to recon's public data sources:

```bash
recon doctor
```

The default diagnostic uses synthetic requests to Microsoft identity endpoints,
DNS for `example.com`, and crt.sh. It does not query a user-supplied target.
The `--fix`, `--mcp`, and `--client` modes are local-only.

Before the first lookup, note that recon makes DNS queries which recursive and
authoritative DNS infrastructure may observe. Its only default request to a
target-owned HTTP endpoint is the standards-defined MTA-STS policy fetch at
`https://mta-sts./.well-known/mta-sts.txt`. Google CSE and BIMI direct
probes run only when `--direct-probes` is explicitly enabled.

Run the first lookup:

```bash
recon contoso.com
```

If a lookup times out or every online source fails, run `recon doctor` to
check source connectivity, then retry the lookup.

Example output shape:

```text
Contoso Ltd
contoso.com

Provider     Microsoft 365 (MX delivery path) + Proofpoint gateway (MX delivery path)
Tenant       a1b2c3d4-e5f6-7890-abcd-ef1234567890
Auth         Federated
Confidence   High (4 sources)

Services
  Email       Microsoft 365, Proofpoint, DMARC, DKIM, SPF strict
  Identity    Okta, Entra ID
  Cloud       Cloudflare, AWS Route 53

Insights
  Federated identity observed; identity-vendor indicators: Okta
  Email security: observed controls: DMARC reject, DKIM, SPF strict, BIMI
  MX gateway observed: Proofpoint
```

Examples use [Microsoft's fictional company names](https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges).
Tenant IDs, services, and domains in examples are fabricated. No real company is
depicted.

For detailed install, update, uninstall, and first-run workflows, read
[docs/getting-started.md](https://github.com/blisspixel/recon/blob/main/docs/getting-started.md).

## What recon Is Good For

| Need | Use recon for | Use something else when |
|---|---|---|
| Fast external stack context | Passive DNS, identity-endpoint, CT, SaaS, and posture indicators | You need authenticated tenant inventory or asset-management truth |
| Defensive review or vendor diligence | Hedged observations and evidence traces you can verify | You need vulnerability scanning, exploit checks, or host-level facts |
| Automation-friendly output | Stable JSON, batch mode, delta mode, and local MCP tools | You need dashboards, scheduling, or report generation built in |

recon reports observations, not verdicts. A missing DMARC record is a missing
record. A Microsoft 365 tenant indicator is an observed indicator. The operator
decides what those facts mean in context.

## Common Commands

```bash
recon contoso.com                              # default panel
recon https://www.contoso.com/path             # normalize URL to apex
recon mail.contoso.com                         # reduce sub-host to apex
recon mail.contoso.com --exact                 # keep that literal host
recon contoso.com --explain                    # retained evidence and explanation
recon contoso.com --full                       # expanded evidence, domains, posture
recon contoso.com --plain                      # linear text for screen readers and grep
recon contoso.com --json                       # structured lookup record
recon batch domains.txt --json                 # batch JSON array
recon batch domains.txt --ndjson               # one record per line
recon batch domains.txt --summary              # aggregate-only cohort summary
recon delta contoso.com                        # diff against cached snapshot
recon cache show mail.contoso.com --exact      # inspect literal-host result and CT cache metadata
recon cache clear mail.contoso.com --exact     # clear literal-host CT and result cache keys
recon mcp install --client=cursor              # wire MCP into a client
recon mcp doctor                               # live MCP handshake check
```

At terminal widths below 70 columns, command help automatically switches to a
complete linear layout so long option names remain visible. `--plain` is the
linear view for a standard single-domain lookup; batch, delta, chain, compare,
exposure, and gaps reports keep their mode-specific formats.

Built-in posture profiles: `fintech`, `healthcare`, `saas-b2b`,
`high-value-target`, `public-sector`, and `higher-ed`. Custom profiles live in
`~/.recon/profiles/*.yaml`.

Generated command and flag reference:
[docs/cli-surface.md](https://github.com/blisspixel/recon/blob/main/docs/cli-surface.md).

## How recon Works

recon reads:

- DNS records: MX, TXT, SPF, DMARC, DKIM, BIMI, CNAME, NS, SRV, and CAA.
- Certificate transparency: SAN names, issuers, issuance timing, and bounded
  related-domain hints.
- Identity discovery: unauthenticated Microsoft and Google endpoints.

Default collection includes bounded DNS queries through the configured
recursive resolver, so authoritative DNS infrastructure may observe resulting
resolver traffic. The only default target-owned HTTP or application request is
the standards-based MTA-STS policy fetch at `mta-sts.`. Google CSE and
BIMI VMC direct probes are opt-in behind `--direct-probes`.

The engine then maps observables to fingerprint slugs, derived signals, typed
topology, provenance paths, per-slug evidence strength, and model-relative
Bayesian diagnostics. Sparse public evidence stays sparse: the result lowers
confidence or remains unresolved instead of inventing a clean answer. A source
failure remains unavailable rather than becoming a negative observation. The
Bayesian uncertainty band is evidence-responsive, not a demonstrated credible
or confidence interval.

The reviewed built-in fingerprint source remains split YAML. Release wheels
load one deterministic generated JSON catalog, while custom and session-scoped
fingerprints still pass through the runtime validator. This keeps contributor
review readable and removes repeated YAML parsing from cold CLI startup without
changing catalog order, matching, or public output.

Long-form explanation:
[docs/how-it-works.md](https://github.com/blisspixel/recon/blob/main/docs/how-it-works.md).
Formal model and robustness research program:
[docs/correlation.md](https://github.com/blisspixel/recon/blob/main/docs/correlation.md).

## JSON and Automation

`recon  --json` emits a stable single-domain lookup object. Batch and
delta modes emit different shapes, so route by mode or by `record_type`.
Retained batch modes create at most the requested number of outer batch worker
tasks while restoring input order. Each admitted lookup may still create its
own bounded source tasks. `--ndjson` also releases completed records and remains
the lowest-memory choice for large inputs.
Batch processing is record-oriented: a valid run keeps exit code 0 when one or
more domains fail. JSON and NDJSON consumers must inspect `record_type` and
`error_kind` on every record; CSV consumers must inspect the `error` column.
`recon batch --summary --json` preserves the separate aggregate-only
`cohort_summary` 2.1 contract. New consumers can select
`--summary-schema 2.2` for raw-evidence-bound DMARC rates, corrected missingness,
and explicit metric kinds. The standalone reducer uses
`--schema-version 2.2` for the corresponding atemporal compatibility view.

```bash
recon contoso.com --json
recon batch domains.txt --json
recon batch domains.txt --ndjson
recon delta contoso.com --json
```

Read these before building an integration:

- [docs/schema.md](https://github.com/blisspixel/recon/blob/main/docs/schema.md): stable JSON contract.
- [docs/recon-schema.json](https://github.com/blisspixel/recon/blob/main/docs/recon-schema.json): machine-readable schema.
- [docs/automation-examples.md](https://github.com/blisspixel/recon/blob/main/docs/automation-examples.md): parser examples.
- [docs/operational-contract.md](https://github.com/blisspixel/recon/blob/main/docs/operational-contract.md): timeouts,
  bounds, exit codes, cache, and partial-result semantics.

`docs/surface-inventory.json`, `docs/cli-surface.md`, and
`recon://surface-inventory` are generated discovery context and drift guards,
not stable runtime API contracts. ADR-0007 records the promotion gate for any
future stable subset.

## MCP Server

The default install includes a local stdio MCP server for MCP-compatible tools.
Start with manual approvals. Approval syntax is client-specific, and some
current client schemas do not define `autoApprove`. Treat connected agents as
untrusted input.

```bash
recon mcp install --client=claude-desktop
recon mcp install --client=cursor --dry-run
recon mcp doctor
```

The installer writes the right per-client config shape and preserves sibling
MCP servers. Full setup, tool list, read-only versus stateful guidance, and
troubleshooting live in
[docs/mcp.md](https://github.com/blisspixel/recon/blob/main/docs/mcp.md).
Per-client scaffolds live in
[agents/](https://github.com/blisspixel/recon/tree/main/agents).

## Limitations

The public channel has a ceiling:

- Internal-only workloads are invisible.
- SaaS products without DNS verification records may not appear.
- Email gateways can hide the downstream mailbox provider.
- CT logs can be stale, partial, rate-limited, or absent.
- Fingerprints are rule-based indicators, not proof of active use.

Read [docs/limitations.md](https://github.com/blisspixel/recon/blob/main/docs/limitations.md)
before using recon output for a high-stakes decision. Read
[docs/data-handling-policy.md](https://github.com/blisspixel/recon/blob/main/docs/data-handling-policy.md)
before committing any validation artifact.

## Documentation

- [docs/getting-started.md](https://github.com/blisspixel/recon/blob/main/docs/getting-started.md): install, update,
  uninstall, and first commands.
- [docs/how-it-works.md](https://github.com/blisspixel/recon/blob/main/docs/how-it-works.md): readable model overview.
- [docs/README.md](https://github.com/blisspixel/recon/blob/main/docs/README.md): complete docs index.
- [docs/roadmap.md](https://github.com/blisspixel/recon/blob/main/docs/roadmap.md): current plan, invariants, and scope
  boundaries.
- [docs/structural-maintainability.md](https://github.com/blisspixel/recon/blob/main/docs/structural-maintainability.md): measured
  source, test, compatibility, and facade cleanup plan.
- [docs/external-writeup-plan.md](https://github.com/blisspixel/recon/blob/main/docs/external-writeup-plan.md): active
  maintainer plan for external write-up readiness.
- [docs/submission-freeze-checklist.md](https://github.com/blisspixel/recon/blob/main/docs/submission-freeze-checklist.md):
  final paper and artifact freeze gate before any external submission package.
- [docs/c3-ct-validation-plan.md](https://github.com/blisspixel/recon/blob/main/docs/c3-ct-validation-plan.md): closed
  certificate-transparency validation plan.
- [CHANGELOG.md](https://github.com/blisspixel/recon/blob/main/CHANGELOG.md): shipped changes.

## Roadmap Focus

recon has a stable baseline, but product quality work remains. The top three
priorities are:

1. Make every default claim traceable to evidence and remove product-use,
   cloud-type, or security-maturity conclusions that public metadata cannot
   support.
2. Keep the exact MCP v1.28.1 and v2.0.0b1 compatibility matrix green, then
   repeat the full gate against the final 2026-07-28 specification and stable
   v2 SDK before changing the production dependency.
3. Establish an aggregate-safe quality baseline for claim precision,
   abstention, provenance, catalog coverage, degradation, latency, CT value,
   and agent context cost before expanding inference or graph machinery.

Catalog coverage work uses deduplicated private rounds across rank, region, and
domain-class strata. Real target names and per-domain records stay in ignored
local validation workspaces. GitHub receives only generic provider patterns,
provider-owned references, fictional fixtures, and disclosure-safe aggregates.
The opt-in maintenance path now accounts separately for CNAME chains, apex
CNAME, non-SPF TXT, SPF targets, MX, NS, CAA, DMARC RUA, bounded owner-qualified
TXT, and bounded SRV observations. A frozen aggregate baseline and distinct
sampling rounds are required before the project claims broad catalog coverage.
The frozen convenience-sample baseline and a 366-namespace unseen vertical
holdout are complete and public as aggregate counts only; independent rank,
regional, vendor-seed, and drift rounds remain open.

The dependency order, acceptance evidence, stop rules, and current code-graph
summary live in
[docs/roadmap.md](https://github.com/blisspixel/recon/blob/main/docs/roadmap.md).
The concise execution sequence is the
[Quality Proof plan](https://github.com/blisspixel/recon/blob/main/docs/strategic-gap-audit.md#quality-proof-execution-plan).
The implementation plan is
[docs/engineering-refinement-plan.md](https://github.com/blisspixel/recon/blob/main/docs/engineering-refinement-plan.md), and
the current step-back review is
[docs/strategic-gap-audit.md](https://github.com/blisspixe

…

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [blisspixel](https://github.com/blisspixel)
- **Source:** [blisspixel/recon](https://github.com/blisspixel/recon)
- **License:** Apache-2.0
- **Homepage:** https://pypi.org/project/recon-tool/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/mcp-blisspixel-recon
- Seller: https://agentstack.voostack.com/s/blisspixel
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.