SnapSweep

dev.snapsweepPublished by snapsweep.devOfficial publisherv1.0.0Updated Oct 25, 2026

Read-only web QA agent: scans a site in a real browser and returns evidence-backed findings

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

A remote, read-only web QA agent that scans a site in a real browser and returns evidence-backed findings to an assistant.

What you can do
Scan a website in a real browser and collect quality-assurance findings, each backed by evidence from the page. The manifest lists no individual tools, so the exact operations are not documented; the described capability is read-only site scanning and reporting. No setup or usage documentation is provided beyond the registry description.
When to use it
Useful when you want an assistant to check a live website for QA issues and get findings tied to concrete page evidence, without running a browser yourself.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is required via OAuth, with a bearer API key sent in the Authorization header, obtained from signup.
Before you install
The server requires an API key in the Authorization header, so treat it as a secret. It scans sites in a real browser, which means the target site and its pages are accessed by a third-party service; confirm you are authorized to scan the site. No tool list or documentation is provided, so the exact scope of what is read or stored is unclear.

Installation

In SourceWeft

  1. Open SnapSweep in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.snapsweep%2Fsnapsweep/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "snapsweep": {
      "type": "http",
      "url": "https://mcp.snapsweep.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 9, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.