1. Conduid
  2. RAG
  3. Vitest MCP Server
MCP server · RAG

Vitest MCP Server

by · github.com/madrus/vitest-mcp-server

Advanced Model Context Protocol (MCP) server for Vitest testing with intelligent resources, coverage analysis, and AI-assisted development workflows

Unclaimed last commit a year ago mcpmodel-context-protocolvitesttestingaiassistantcursordevelopmentcoverageautomation
InstallView source
37Low

Scored 4 hours ago · breakdown

About Vitest MCP Server

Vitest MCP Server is an MCP server published by madrus in the RAG category: advanced Model Context Protocol (MCP) server for Vitest testing with intelligent resources, coverage analysis, and AI-assisted development workflows.

The repository has 3 stars and 0 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

Claude Code
claude mcp add vitest-mcp-server-7899 -- npx -y @madrus/vitest-mcp-server
npx
npx -y @madrus/vitest-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Vitest MCP Server

Powered by Claude · Grounded in docs

I know everything about Vitest MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Vitest MCP Server

How do I install Vitest MCP Server?

Run claude mcp add vitest-mcp-server-7899 -- npx -y @madrus/vitest-mcp-server, then add the server to your MCP client's configuration.

Is Vitest MCP Server safe to use with an AI agent?

Its trust score is 37 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Vitest MCP Server still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.