test-intel-mcpSAFE
Local test coverage intelligence for JavaScript and TypeScript: gaps, complexity, and practical test priorities over MCP or CLI.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Turn JavaScript and TypeScript coverage artifacts into practical test priorities. The server reads local coverage and source files, identifies gaps, scores function complexity, and suggests focused test cases without sending code to an external service.
Tool page · npm · Listed in the official MCP Registry
Start in one minute
Add one local server entry to any stdio-compatible MCP client:
{
"mcpServers": {
"test-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/test-intel-mcp"]
}
}
}Then ask the client to inspect an existing coverage file:
Use t
abf4bb586b68OBSERVED · 2026-10-11Connect
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 test-intel-mcp -- npx -y @barissozudogru/[email protected]
Exposed tools (4)
4 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
analyze_test_coverage | read | |
find_untested_functions | read | |
get_function_complexity | read | |
suggest_test_cases | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
process.stderr.write(`test-intel-mcp v${VERSION} listening on http://0.0.0.0:${port}/mcp\n`);"tests/__tests__/thing.ts": 'import { computeA } from "../../src/thing.js";\n\ncomputeA(2);\n',@modelcontextprotocol/sdk, express, zod, @types/express, @types/node, typescript
Gates applied: no_behavioural_pass.
abf4bb586b68full audit observations/trust-audit/mcp-server/barissozudogru__test-intel-mcp.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-11 | abf4bb586b68 | SAFE | B | 89 | first audit |
Questions
What is the test-intel-mcp MCP server?
Local test coverage intelligence for JavaScript and TypeScript: gaps, complexity, and practical test priorities over MCP or CLI.
What tools does test-intel-mcp 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 test-intel-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does test-intel-mcp need?
No credential environment variables were found in its source, so it appears to need none.
How does test-intel-mcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @barissozudogru/test-intel-mcp at 0.8.5.
How current is this page?
The grade is for one exact copy of the source (abf4bb586b68), read on 2026-10-11. The repository is watched and re-audited when it changes.