Claude Tools / Plugins / testdino
Audited plugin listing
testdino
Connects Claude Code to the TestDino hosted MCP server for inspecting test runs, debugging failing cases, and managing manual test suites.
Listing signals
Install check
✓ Pass
Risk scan
✓ Clean
Implementation
Prompt-only
Assessment
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.
Installation
Add to Claude Code
Evidence
Audit receipts
This listing is tied to a specific source commit and records both installation and risk checks.
Install check
✓ Pass
Seven skills routing to MCP tools on mcp.testdino.com. No local code. MCP URL declared in .mcp.json.
Risk scan
✓ Clean
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.
Composition
What was measured
Prose lines
357
Code lines
0
Prose / code
99.00
Related