Frontend TestingBLOCK
Frontend testing tools for Model Context Protocol
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Description
This MCP server provides tools for frontend testing, including:
- Code Analysis: Analyzes JavaScript/TypeScript code to determine appropriate testing strategies.
- Test Generation: Generates unit and component tests for Jest and Cypress.
- Test Running: Executes tests using Jest and Cypress and returns results.
- Component Testing: Provides a tool specifically for testing React components.
Getting Started
Installation
- Clone the repository:
\git clone mcp-frontend-testing\
- Navigate to the project directory:
\cd mcp-frontend-testing\
- Install dependencies:
\npm install\
Running the Server
HTTP Transport
\\\`bash
Build the server
npm run build
Start the server with HTTP transport
npm run start:http \\\`
Stdio Transport
\\\`bash
Build the server
npm run build
Start the server with Stdio transport
npm run start:stdio \\\`
Usage
Tools
- analyzeCode: Analyzes code and returns analysis results.
- Parameters:
- \
code\(string, required): The source code to analyze. - \
language\(enum, optional): Language of the code (\javascript\| \typescript\| \jsx\| \tsx\, default: \javascript\). - generateTest: Generates test code based on source code and framework.
- Parameters:
- \
code\(string, required): The source code to generate tests for. - \
framework\(enum, required): Testing framework (\jest\| \cypress\). - \
type\(enum, required): Type of test (\unit\| \component\| \e2e\). - \
language\(enum, optional): Language of the code (\javascript\| \typescript\| \jsx\| \tsx\, default: \javascript\). - \
description\(string, optional): Description of the test case. - runTest: Runs tests and returns results.
- Parameters:
- \`sourceCod
3b323ed5cae3OBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-frontend-testing -- npx -y [email protected]
{
"mcpServers": {
"mcp-frontend-testing": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (4)
4 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
analyzeCode | read | |
generateTest | read | |
runTest | read | |
testReactComponent | read |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (2 observation(s))
- Network
- declared (2 observation(s))
- Shell
- declared (2 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (5)
exec(command, { cwd }, (error, stdout, stderr) => {exec(command, { cwd }, (error, stdout, stderr) => {const templatesDir = path.join(__dirname, '../../templates');
const templatesDir = path.join(__dirname, '../../templates');
@testing-library/jest-dom, @testing-library/user-event, cors, jest, jest-environment-jsdom, @types/cors, @types/jest, ts-node
Gates applied: no_behavioural_pass.
3b323ed5cae3full audit observations/trust-audit/mcp-server/studentofjs__frontend-testing.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 3b323ed5cae3 | BLOCK | D | 69 | first audit |
Questions
What is the Frontend Testing MCP server?
Frontend testing tools for Model Context Protocol
What tools does Frontend Testing expose?
4 in total: 4 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Frontend Testing safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 2 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does Frontend Testing need?
No credential environment variables were found in its source, so it appears to need none.
How does Frontend Testing run?
It speaks sse and stdio, so it runs as a local process your client starts. It is published on npm as mcp-frontend-testing at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (3b323ed5cae3), read on 2026-10-09. The repository is watched and re-audited when it changes.