web-exposure-mcp

scan_web_exposure

Probe a live URL to detect exposed sensitive files like .git, .env, source maps, backups, and directory listings, with content-based verification to avoid false positives.

Instructions

Probe a LIVE deployed URL and confirm which sensitive files/directories are actually publicly reachable — by fetching the bytes, not guessing. Detects exposed .git, .env secrets, JavaScript source maps, backup/SQL dumps & archives (.bak/.sql/.zip), directory listing, and sensitive dotfiles (.htpasswd/.npmrc/.aws/credentials/.ssh/id_rsa). Read-only: nothing is written to the target. Returns only findings that are genuinely served, with evidence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "scan_web_exposure"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The live base URL to scan, e.g. https://example.com (scheme optional, defaults to https).
`only`	No	Optional: run only these check ids. Omit to run all.
`timeout_ms`	No	Optional per-request timeout in milliseconds (default 10000).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description explicitly states 'Read-only: nothing is written to the target' and emphasizes direct byte-fetching rather than guessing. However, it does not discuss rate limits, authentication needs, or potential impact on target, which would be beneficial given no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, front-loaded with the core purpose, lists specific checks, and includes a brief read-only note. Every sentence adds value, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's function, checks performed, and output nature (genuine findings with evidence). Given the absence of an output schema, it provides adequate context, though it could further detail the output structure or non-functional aspects like parallelism.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already describes all parameters. The description adds no additional insight over the schema, such as format constraints or usage tips, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool probes a live URL to confirm sensitive exposures, listing specific file types. It differentiates from sibling 'list_exposure_checks' which likely lists available checks rather than performing scans.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (for active scanning) but does not explicitly contrast with alternatives or state when not to use it. Sibling tool 'list_exposure_checks' is mentioned but no direct guidance on switching between them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server