1. Conduid
  2. Developer Tools
  3. Testing MCP Vitest
MCP server · Developer Tools

Testing MCP Vitest

by · github.com/fyuuki0jp/testing-mcp-vitest

vitest test code generetor in mcp (claude code used)

Unclaimed last commit a year ago devtools
InstallView source
34Low

Scored a month ago · breakdown

About Testing MCP Vitest

Testing MCP Vitest is an MCP server published by fyuuki0jp in the Developer Tools category: vitest test code generetor in mcp (claude code used).

The repository has 2 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

From source
git clone https://github.com/fyuuki0jp/testing-mcp-vitest

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.

Tools (3)

boundary-value-exampleProvides boundary value analysis examples

Parameters not published.

create-test-specExplains how to create test specifications

Parameters not published.

equivalence-class-exampleProvides equivalence partitioning examples

Parameters not published.

Ask AI

✦

Ask AI about Testing MCP Vitest

Powered by Claude · Grounded in docs

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

Security checks

6 checks have not been run yet.

Questions

About Testing MCP Vitest

How do I install Testing MCP Vitest?

No package has been published for this server, so install it from source: clone the repository and follow its README.

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

Its trust score is 34 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 Testing MCP Vitest 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.