vibe-testing

MCP server · npm · ★ 17 · graded 2026-10-24Source linked

Code-aware browser testing for AI coding agents. Reads your codebase so tests use real routes and field names, runs them in Playwright, remembers what broke, and reports what your last change fixed or regressed. No LLM calls inside. MCP server for Claude

No outside reports on file

vibe-testing fetches arbitrary web URLs; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Vibe Testing helpful?

What it can access

Local filesNo local folder access notedLOW
Command executionNo shell command runner notedLOW
Network reachFetches arbitrary web URLsREVIEW
CredentialsNo API token requiredLOW
Package sourcenpm (vibe-testing)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

npx -y vibe-testing

All setup options ↓

Check this skill Watch it in my stack Compare README badge View project

Everything known

We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.

0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30

Popularity grade: C (from public signals such as stars and downloads, not a code review). Graded 2026-10-24.

Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.

Check a specific version →

About Vibe Testing

Vibe Testing is an MCP server focused on Developer tools and Web & browsing: Code-aware browser testing for AI coding agents. Reads your codebase so tests use real routes and field names, runs them in Playwright, remembers what broke, and reports what your last change fixed or regressed. No LLM calls inside. MCP server for Claude.

It is published on npm as vibe-testing and hosted on GitHub at aishwaryshrivastav/vibe-testing (17 GitHub stars, 72 weekly npm downloads, last repository push on 2026-10-15). Based on its public metadata, its operational scope includes: fetches arbitrary web urls.

Setup

Check these steps against the project’s own instructions before running anything.

Run vibe-testing with --ignore-scripts in claude_desktop_config.json or .cursor/mcp.json:

json

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": ["-y", "--ignore-scripts", "vibe-testing"]
    }
  }
}

Why this grade

CC — Moderate risk signals

Signal-based grade (2/7 points): listed in several sources, public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

39/100

GitHub stars: 17
Weekly npm downloads: 240
Listing last refreshed: 2026-10-30

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Risks to watch for

Untrusted web content & prompt injection: Fetches arbitrary web pages or remote endpoints where hidden instructions could manipulate agent behavior. Restrict outbound domains and review tool outputs.
Dependency & version pinning: Distributed via npm (vibe-testing). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

Check its activity history or logs weekly at first, and look at what it changed or sent.
Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

It asks for more access than its job requires, or prompts you to paste passwords.
It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install Vibe Testing?

Run npx -y vibe-testing in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/aishwaryshrivastav/vibe-testing.

Are there security reports about Vibe Testing?

No reports found for this package in our research (last checked 2026-10-30). Vibe Testing currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include untrusted web content & prompt injection:, dependency & version pinning:.

Is Vibe Testing actively maintained?

Vibe Testing has 17 GitHub stars and 240 weekly npm downloads, with its latest repository commit pushed on 2026-10-15. Our directory data was last refreshed on 2026-10-30. Check recent commit activity, release tags, and open issues at github.com/aishwaryshrivastav/vibe-testing before pinning it in production.

What are alternatives to Vibe Testing?

You can compare Vibe Testing side by side with other Browser, Playwright MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

Maintain or use Vibe Testing? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade C for Vibe Testing

GitHub README Markdown:

markdown

[![AgentArmorHQ Risk Grade for Vibe Testing](https://agentarmorhq.com/api/badge/aishwaryshrivastav-vibe-testing)](https://agentarmorhq.com/skills/aishwaryshrivastav-vibe-testing)

HTML embed:

html

<a href="https://agentarmorhq.com/skills/aishwaryshrivastav-vibe-testing"><img src="https://agentarmorhq.com/api/badge/aishwaryshrivastav-vibe-testing" alt="AgentArmorHQ Risk Grade for Vibe Testing" height="20" /></a>

Terminal check:

terminal

curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "aishwaryshrivastav-vibe-testing"

Share with your security lead

Need sign-off to use vibe-testing? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: vibe-testing
- **Listing URL:** https://agentarmorhq.com/skills/aishwaryshrivastav-vibe-testing
- **Type:** App connector
- **Risk Grade:** Grade C (Moderate risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 17 GitHub stars, 240 weekly npm downloads

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Fetches arbitrary web URLs
- **Credentials:** No API token required
- **Package source:** npm (vibe-testing)

#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts vibe-testing`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type: App connector
Publisher: aishwaryshrivastav
Source code: github.com/aishwaryshrivastav/vibe-testing
Install command: npm install vibe-testing
Est. context load: ~600 tokens / turn (~3 tool schemas, 0.3% of 200k context)
Popularity: 17 GitHub stars, 240 weekly npm downloads
Last updated: 2026-10-30
Last graded: 2026-10-24

Community

Discussions for Vibe Testing

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for Vibe Testing helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude