
Test Shape Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026
Audit local test structure using aggregate assertions without returning test names, paths, or...
Overview
A local MCP server that gives an assistant aggregate structural counts of a project's test suite without exposing test names, paths, or code.
- What you can do
- Inspect a local project's test suite structure with a single tool, inspect_test_shape.
- Get aggregate counts of test blocks, suites, async tests, assertion-bearing files, and empty test bodies.
- Review the shape of a test suite for triage without seeing test names, paths, source, or assertion details.
- When to use it
- Useful when you want a quick, privacy-preserving overview of how a local test suite is structured, for example to spot empty test bodies or files with assertions before a review. It is a triage aid, not a substitute for running the tests.
- Requirements
- Runs as a local process over stdio, installed from the npm package test-shape-mcp; a Node.js runtime and a local project with test files are needed. No authentication, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Test Shape Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
test-shape-mcp
Test Shape gives a quick structural view of a local test suite. It counts test blocks, suites, async tests, assertion-bearing files, and empty test bodies without exposing test names or code.
Quick start
Use inspect_test_shape against a local project. Results are heuristics for review triage, not a replacement for running tests.
Privacy and limits
Only bounded local test files are read. The response contains aggregate counts only. Test names, paths, source, and assertion details are suppressed.
Source: README.md at commit 341820d
Tools
0Version history
1- v1.0.0LatestSep 22, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.