Tada: automated QA for AI-written code

dev.taadaPublished by taada.devv0.1.44Updated Oct 24, 2026

Your coding agent asks Tada to work through a feature in a real browser and gets back a verdict.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Lets a coding agent hand a feature to Tada, which exercises it in a real browser and returns a verdict.

What you can do
Tada is an automated QA server for AI-written code. According to its description, a coding agent asks Tada to work through a feature in a real browser and receives a verdict back. No tool list is published in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant writes code and you want that code exercised in a real browser before you trust it. It suits teams that want automated verification of agent-produced features rather than manual checking.
Requirements
Runs as a local process over stdio, installed from the npm package tada-mcp, so a Node.js runtime is needed. Desktop only; no web executable. The manifest declares no authentication, environment variables or headers.
Before you install
The manifest declares no credentials, but the server drives a real browser, so it may interact with live pages and accounts. Review what it can reach before running it against production or signed-in sessions.

Installation

In SourceWeft

  1. Open Tada: automated QA for AI-written code in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.44LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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