Skip to main content

FSV — finds what checklists miss

FSV — web security scanner & MCP server

For the problems nobody is watching: dangling DNS and subdomain takeover, orphaned cloud buckets, scripts from compromised or expired CDN domains, SPF includes that no longer exist, debug mode left on in production, secrets in your JavaScript, end-of-life software — and the attack paths that turn small findings into a real compromise, each with the cheapest fix that breaks it.

Runs as a CLI, a dashboard, an MCP server for AI assistants (Claude, Cursor, VS Code), and a CI step. Detection only: it never exploits, never claims a resource, never tests a credential.

Authorized use only. Scan only systems you own or are explicitly authorized in writing to test.

Install

pip install fsv            # Python 3.11+
fsv doctor                 # checks dependencies, DNS, database

Scan

fsv scan example.com --authorize                     # full scan of a site you own
fsv scan example.com --authorize --profile passive   # read-only: no payloads sent
fsv fixes <scan_id> nginx                            # paste-ready config for what was found
fsv web                                              # dashboard → http://127.0.0.1:7474

Connect your AI assistant

fsv mcp-config --client claude-code      # prints:  claude mcp add fsv -- /path/to/fsv-mcp
fsv mcp-config --client claude-desktop   # or: cursor · vscode

Then ask: “Use the security_review prompt on https://my-site.example — I own it.” The assistant confirms authorization, runs a passive check and a full scan, leads with attack paths and hands you the fixes.

What it finds

Detection cards: dangling DNS, orphaned bucket, dead SPF include, source map and secrets, end-of-life software, attack path, compromised CDN, debug mode

32 modules — DNS takeover, cloud storage, script supply chain, SPF/DMARC/DKIM, JavaScript secrets and source maps, vulnerable and end-of-life libraries, ~100 content-validated exposure checks, framework debug pages, headers/CSP/cookies, and benign active checks for common reflected issues. Findings carry severity, confidence, CWE, OWASP Top 10 category and remediation; reports in Markdown, JSON, HTML, SARIF and CSV.

License: FSV Personal Use License — free for personal, educational and non-commercial security research. Commercial use is prohibited (see LICENSE); licensing questions: statways1707@gmail.com.

Metadata

Release files for fsv 2.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fsv 2.1.0
File Size Uploaded Provenance
fsv-2.1.0.tar.gz 213.7 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for fsv 2.1.0
File Interpreter ABI Platform
fsv-2.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 414.4 kB

Release files / fsv-2.1.0.tar.gz

Download URL fsv-2.1.0.tar.gz
Size 213.7 kB
Tags Source
SHA-256 checksum
How to use checksums
cd38d65194b73a9da9847be5f5afbb3fe40c90ae2911a9d8d2a4e6425b86d655
BLAKE2b-256 checksum
How to use checksums
00e0d547ddd0b55a44193aacbf960ef220542ece806c880e3f29a8df86129055
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

Release files / fsv-2.1.0-py3-none-any.whl

Download URL fsv-2.1.0-py3-none-any.whl
Size 200.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
84cc86c53baa8c4c65913dc55496b747009f87cb3b7883d2ceda0328b9726f6a
BLAKE2b-256 checksum
How to use checksums
1b13c91b9bb22107726a2e561506eb98be357d3f540c831aeb1cc5cba85a9712
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

Security for fsv 2.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for fsv-2.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page