SyntheticUser Lab MCP

space.syntheticuserlabPublished by syntheticuserlab.spaceOfficial publisherv0.1.0Updated Oct 25, 2026

Paid remote MCP for synthetic user testing, UX validation, analytics, checkout, and readiness.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A paid remote MCP server for synthetic user testing and UX validation, giving an assistant a way to run simulated user checks and readiness analytics.

What you can do
Run synthetic user testing and UX validation against a product or interface, per the registry description. Access analytics and readiness information related to those tests. Handle checkout and token claiming for the paid service. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Consider it when you want an assistant to help evaluate a product's user experience or readiness through simulated users rather than real participants, and you are prepared to pay for the service.
Requirements
A remote streamable HTTP endpoint at syntheticuserlab.space. A bearer token sent in the Authorization header, issued after checkout and an MCP token claim; no environment variables or local packages are declared.
Before you install
This is a paid service: a checkout step is required before a token is issued, so expect a purchase. The Authorization bearer token is a secret and should be kept private. The manifest lists no tools, so what the server can read or change is not documented; review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open SyntheticUser Lab MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/space.syntheticuserlab%2Fsyntheticuserlab-mcp/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.

{
  "mcpServers": {
    "syntheticuser-lab": {
      "type": "http",
      "url": "https://syntheticuserlab.space/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% 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.

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