Registries mcp.so TTestdino McpTestDino MCP is a Model Context Protocol server that lets AI agents work directly with your Playwright test data, without leaving your editor or opening a browser. Once connected, your AI assistant can browse TestDino runs, inspect failing tests, and manage manual cases using plain language. Ask it to “show the last 5 failed runs in production,” “debug the checkout flow test,” or “list all critical manual test cases in project X,” and it will call the right tools behind the scenes. The server exposes 12 focused tools for CI runs, debugging, and manual test management. You can: Check account health and validate your PAT Filter runs by branch, commit, author, time window, or environment Drill into a single test case, including errors, logs, steps, screenshots, and traces Run debug_testcase to aggregate historical failures, classify patterns, and get AI‑ready prompts for root‑cause analysis and flakiness Create, update, and organize manual test cases and suites (status, severity, tags, layers, behaviors) TestDino MCP is MCP‑compatible and works with clients like Cursor and Claude Desktop. Configure it via mcp.json using either npx testdino-mcp (no install) or a global install (npm install -g testdino-mcp), and provide a TESTDINO_PAT from your TestDino account. Typical use cases include: speeding up Playwright failure triage from within your IDE, giving AI agents structured access to real test history, and keeping manual test management in sync with how your team actually debugs CI.

TTestdino McpTestDino MCP is a Model Context Protocol server that lets AI agents work directly with your Playwright test data, without leaving your editor or opening a browser. Once connected, your AI assistant can browse TestDino runs, inspect failing tests, and manage manual cases using plain language. Ask it to “show the last 5 failed runs in production,” “debug the checkout flow test,” or “list all critical manual test cases in project X,” and it will call the right tools behind the scenes. The server exposes 12 focused tools for CI runs, debugging, and manual test management. You can: Check account health and validate your PAT Filter runs by branch, commit, author, time window, or environment Drill into a single test case, including errors, logs, steps, screenshots, and traces Run debug_testcase to aggregate historical failures, classify patterns, and get AI‑ready prompts for root‑cause analysis and flakiness Create, update, and organize manual test cases and suites (status, severity, tags, layers, behaviors) TestDino MCP is MCP‑compatible and works with clients like Cursor and Claude Desktop. Configure it via mcp.json using either npx testdino-mcp (no install) or a global install (npm install -g testdino-mcp), and provide a TESTDINO_PAT from your TestDino account. Typical use cases include: speeding up Playwright failure triage from within your IDE, giving AI agents structured access to real test history, and keeping manual test management in sync with how your team actually debugs CI.

mcp-so:testdino-mcp_testdino-hq

View source

92/100

First Seen

Feb 18, 2026

Last Scanned

Feb 20, 2026

Findings

Score

92/100

MEDIUM 1

LOW 2

Findings (3)

MEDIUM

Auto-confirm flag bypassing user verification MCPCFG_008

mcp-config L120

Detects -y, --yes, or --auto-approve flags in MCP/skill install commands that bypass user confirmation

"-y"

FIX

Remove the -y/--yes auto-confirm flag from MCP server launch arguments. This flag bypasses user confirmation prompts and allows unattended execution of potentially dangerous operations.

FP?

Likely FP if the matched text is an isolated flag (-y or --yes) in documentation describing command-line options, not in an actual MCP config.

LOW

Global package installation EXTDL_004

external-download L40

Detects global installation of packages which affects the host system

npm install -g t

FIX

Replace npm install -g with a local install (npm install --save-dev) or use npx with a pinned version. Global installs modify the system and risk supply chain attacks.

FP?

Likely FP if the global install is for a well-known CLI tool (e.g., typescript, eslint) in setup documentation, though the supply chain risk remains real.

LOW

npx MCP server without version pin MCPCFG_001

mcp-config L118

Detects MCP server configs using npx to run packages without version pinning

"command": "npx"

FIX

Pin the npx package in the MCP config to an exact version (e.g., @scope/server@1.2.3). Unpinned npx commands can silently fetch a compromised package version.

FP?

Likely FP if the MCP config is a local development setup example, though unpinned npx in production configs is a real supply chain risk.