ASMHunter

app.asmhunterPublished by asmhunter.appv0.1.2Updated Oct 24, 2026

Drive ASMHunter attack-surface monitoring from an AI agent: recon, scans, findings, reports.

The publisher's own server: Hunter Lease

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

ASMHunter MCP lets an AI assistant drive ASMHunter attack-surface monitoring: recon, scans, findings and reports, from a local process.

What you can do
  • Run reconnaissance and scans against monitored attack surfaces.
  • Review and triage findings produced by those scans.
  • Produce or retrieve reports on attack-surface status.
  • All actions are performed through the ASMHunter service using a personal access token.
When to use it
Useful when you already rely on ASMHunter for attack-surface monitoring and want an assistant to trigger recon or scans, review findings, and pull reports without switching to the web app.
Requirements
Runs as a local stdio process, installed from the asmhunter-mcp PyPI package, so a Python environment is needed. Requires the ASMHUNTER_TOKEN environment variable holding an ASMHunter personal access token, which must be minted in the ASMHunter settings under API tokens and needs a Hunter tier account or above. Desktop only; network access to ASMHunter is implied.
Before you install
The ASMHUNTER_TOKEN is a live credential granting API access to your ASMHunter account; keep it out of logs and shared configs. Scans and recon act on real external systems, so confirm targets before letting an assistant start them. Findings and reports may contain sensitive security data sent to the ASMHunter service.

Installation

In SourceWeft

  1. Open ASMHunter in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Hunter integrations