Directory / testdino
testdino
PromisingConnects Claude Code to the TestDino hosted MCP server for inspecting test runs, debugging failing cases, and managing manual test suites.
Verdict
Testdino is a minimal MCP router: seven short skills that tell Claude which TestDino tool to call for each QA workflow — list runs, inspect failures, debug historical patterns, manage manual tests. The plugin files themselves contain no executable code; all logic lives on the remote server at mcp.testdino.com. That remote surface is the real trust boundary, and this audit can only observe that it is fully disclosed, not that it is safe. Teams already using TestDino for Playwright automation will find this useful; teams evaluating TestDino should audit the service itself before adoption.
Install
Audit receipts
Every listing is verified against a specific commit. These are the receipts.
Seven skills routing to MCP tools on mcp.testdino.com. No local code. MCP URL declared in .mcp.json.
mcp.testdino.com is fully disclosed in .mcp.json and plugin.json homepage. All execution happens server-side via authenticated MCP; the local plugin files are routing guides only. The remote server is the actual code surface — not inspectable from this audit.