Before Users Do

io.github.bhuman-aiPublished by GitHub account bhuman-aiv1.0.0Updated Nov 4, 2026

Browser-backed QA with evidence and fix-ready reports for coding agents.

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Remote MCP server that gives coding agents browser-backed QA runs with evidence and fix-ready reports.

What you can do
  • Run browser-backed QA checks on a web app and collect evidence from the results.
  • Produce fix-ready reports that a coding agent can act on.
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in.
When to use it
Useful when a coding agent should verify web UI behavior in a real browser and get back evidence plus a report it can turn into fixes, rather than relying on code inspection alone.
Requirements
A remote MCP endpoint at mcp.beforeusersdo.com over streamable HTTP. OAuth authentication is required; the client sends an Authorization header. No local package or environment variables are declared.
Before you install
The server requires OAuth authorization, so it receives an access token via the Authorization header. QA runs act on a live web application, so point it only at sites you are authorized to test. The manifest lists no tools, so review the provider's documentation before granting access.

Installation

In SourceWeft

  1. Open Before Users Do 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/io.github.bhuman-ai%2Fbeforeusersdo/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": {
    "before-users-do": {
      "type": "http",
      "url": "https://mcp.beforeusersdo.com/mcp"
    }
  }
}

README

This repository has no README.

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.0LatestSep 16, 2026

Score

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