Bragproof

← Reports

tada-mcp

Starts with no setup0.2.4npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 3 tools tried
Contacts while installing and starting: nothing

16tools listed
0hosts contacted
0files written
0.5 sto start
118dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y -p tada-mcp@0.2.4 tada-mcp

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

3 tools that take no input and look read-only were called once with nothing. 0 returned a result.

about_appNo usable answer tool reported an error: Not signed in to Tada, so nothing was done. Run `tada login` in a terminal (it opens a browser to authorize), then call this tool again.
connect_statusNo usable answer tool reported an error: Not signed in to Tada, so nothing was done. Run `tada login` in a terminal (it opens a browser to authorize), then call this tool again.
tada_connect_statusNo usable answer tool reported an error: Not signed in to Tada, so nothing was done. Run `tada login` in a terminal (it opens a browser to authorize), then call this tool again.

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

about_app repo
Read what Tada knows about an app before you create a test for it: a test account that cannot sign in (first, with its fix), its features and tests, its test accounts, its screens, and what is still to connect. Free; changes nothing.
create_test goal, role, address, repo, title, feature, ticket, steps, tests, device, initScript, hideSelectors, signIn, presentation
Create a test of a feature and check it in a real browser on Tada's side: a `goal` (Tada writes the test) or `steps`; a step `{ action: "expect", text: "Untitled form", absent: true }` checks that it is NOT on the page. The answer leads with the verdict, Passed, Failed or Inconclusive, then what to do, with the report's link. An app on localhost is reached through a tunnel.
check_test repo, test, tags, match, presentation
Check a saved test again now, by its name (or a feature's, or tags), or every switched-on test of the app. Answers with the verdict and the report.
update_test test, repo, changes, reason, pr, address, undo
Change a saved test when the app changed on purpose: find a step a new way (selector, text, anyOf), put in steps or checks, with a `reason` and the pull request in `pr`. Never weakens a check, an absent check included; the revised test is replayed first and only a pass saves. `undo` takes a change back.
read_report id
Read a check by its id: waiting, going, or its verdict and report. Read only.
11 more tools
cancel_check id
Stop a check by its id: one waiting for a runner ends at once, one going stops at its next step. Not billed, never a pass.
create_test_account repo, role, email, password, environment
Make a test account a test can sign in as (`role`), or hand Tada one you seeded (`role`, `email`, `password`).
plan_tests repo, title, ticket, text, acceptanceCriteria, pages, roles, setup, changed, outOfScope, proposal
Send a ticket, get the rules its tests must meet; send your tests as `proposal` to have them held to those rules.
connect_status
See what this Tada workspace still needs connected to check pull requests, with the link for each.
check_feature goal, role, address, repo, title, feature, ticket, steps, tests, device, initScript, hideSelectors, signIn, presentation
Old name for create_test; use create_test.
verify_feature goal, role, address, repo, title, feature, ticket, steps, tests, device, initScript, hideSelectors, signIn, presentation
Old name for create_test; use create_test.
record_demo goal, role, address, repo, title, feature, ticket, steps, tests, device, initScript, hideSelectors, signIn, presentation
Old name for create_test; use create_test.
check_result id
Old name for read_report; use read_report.
setup_test_account repo, role, email, password, environment
Old name for create_test_account; use create_test_account.
plan_feature repo, title, ticket, text, acceptanceCriteria, pages, roles, setup, changed, outOfScope, proposal
Old name for plan_tests; use plan_tests.
tada_connect_status
Old name for connect_status; use connect_status.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

Licensenot stated
Needsnode >=20
Sourcenot stated
Install scriptscloudflared, ffmpeg-static, fsevents, tada-mcp declare them. This runner does not run them.
Tarballsha512-sRgrQAx8tFuFpXlGKoc+Dwp8a0n/44lAIvlIbUsyXsdyqRGanGsP/gJXvShmBlrO0kRa87RvZ8TSr2esQtB3Lw==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/tada-mcp.svg)](https://bragproof.smaverk.com/r/tada-mcp)

New version out? Ask for a fresh report.