Web Recon Agent

io.github.joepangalloPublished by GitHub account joepangallov0.8.1Updated Oct 24, 2026

Owned-target web security assessment MCP server for authenticated, high-friction apps.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local MCP server for owned-target web security assessment, letting an assistant run scan jobs against hostnames you allowlist.

What you can do
  • Run web security scan jobs against hostnames you have allowlisted, aimed at authenticated, high-friction applications.
  • Unlock active and owned-aggressive scan modes for hostnames you explicitly declare as owned.
  • Persist job metadata to a JSON file so scan jobs can be tracked across sessions.
  • Tune scanning through a JSON config file that overrides allowlist and concurrency settings.
  • Limit how many scan jobs run at once via a concurrency setting.
When to use it
Use it when you want an AI assistant to help assess the security of web applications you own or are authorized to test, especially authenticated apps that resist ordinary scanning. It is not meant for scanning third-party sites.
Requirements
Runs as a local stdio process installed from the npm package mcp-web-recon-agent, so Node.js is needed. MCP_TARGET_ALLOWLIST is required and lists the hostnames allowed for scanning. Optional settings: MCP_OWNED_TARGETS for owned hostnames, MCP_CONFIG_PATH for a JSON config file, MCP_JOB_STORE_PATH for job metadata, and MCP_MAX_CONCURRENT for concurrency. No authentication is declared.
Before you install
Scanning sends traffic to the listed hosts and can be intrusive; only allowlist hostnames you own or are explicitly authorized to test, and treat MCP_OWNED_TARGETS as a claim of ownership that unlocks more aggressive modes. Job metadata is written to a local JSON file (mcp-jobs.json by default) in the working directory, which may record target details.

Installation

In SourceWeft

  1. Open Web Recon Agent 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.8.1LatestSep 16, 2026

Score

25% 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
  • 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.