Validatethat Mcp

io.github.RyanByrnePublished by GitHub account RyanByrnev0.1.0Updated Oct 24, 2026

Run UX research from Claude — create card sort studies, list studies, pull headline stats.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Lets an assistant run UX research in Validatethat: create card sort studies, list existing studies, and pull headline stats.

What you can do
This remote MCP server connects an assistant to Validatethat's UX research platform. According to the registry description, it can create card sort studies, list studies, and pull headline stats. It is hosted at validatethat.io and reached over streamable HTTP rather than installed locally.
When to use it
Use it when you want to set up or review UX research studies without leaving the assistant, for example creating a card sort, checking which studies exist, or grabbing summary numbers for a report. It suits teams already using Validatethat for research work.
Requirements
A remote streamable HTTP endpoint at reachable over the network. Authentication is required: a bearer API token supplied in the Authorization header, generated from the Validatethat dashboard integrations settings. No local runtime or packages are needed.
Before you install
The server requires a bearer token sent in the Authorization header, so treat that token as a secret and avoid exposing it in shared logs or transcripts. Creating studies writes data to your Validatethat account, and the assistant's requests and study content are sent to a third-party service.

Installation

In SourceWeft

  1. Open Validatethat 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/io.github.RyanByrne%2Fvalidatethat-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": {
    "validatethat": {
      "type": "http",
      "url": "https://validatethat.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.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 listedRequired15 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.