Test Intel
NPM · @BARISSOZUDOGRU/TEST-INTEL-MCP
Coverage analysis, untested function detection and complexity scoring for TS and JS.
Available components
Last scanned (7 hours ago)
Scores higher than 65% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 70 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 285 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 −1
- Stability: pass → 0.93 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@barissozudogru/test-intel-mcp@0.8.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_test_coverage Analyze Test Coverage ~84
Parse a coverage report (lcov, istanbul JSON, or cobertura XML) and return uncovered files, functions, lines, and branch gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_path | string | yes | Path to the coverage file (lcov.info, coverage-summary.json, coverage.xml, etc.) |
| format | string | – | Coverage format. Auto-detected from file extension if omitted. |
No output schema declared.
No examples provided.
find_untested_functions Find Untested Functions ~98
Scan source files for function/method declarations and identify those with no corresponding test file.
| Name | Type | Req | Description |
|---|---|---|---|
| extensions | array | – | File extensions to include, e.g. [".ts", ".js"]. Defaults to [".ts", ".tsx", ".js", ".jsx"]. |
| source_dir | string | yes | Directory containing source files to scan. |
| test_dir | string | – | Directory containing test files. Defaults to same directory as source. |
No output schema declared.
No examples provided.
get_function_complexity Get Function Complexity ~43
Analyze a file's functions for cyclomatic complexity to prioritize which functions need tests most urgently.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the source file to analyze. |
No output schema declared.
No examples provided.
suggest_test_cases Suggest Test Cases ~60
Analyze a specific function and generate structured test case suggestions based on its logic, branches, and type signatures.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the source file containing the function. |
| function_name | string | yes | Name of the function to analyze. |
No output schema declared.
No examples provided.
How do I install the Test Intel MCP server?
Test Intel runs locally as an npm package, launched with npx -y @barissozudogru/test-intel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @barissozudogru/test-intel-mcp
claude mcp add barissozudogru-test-intel -- npx -y @barissozudogru/test-intel-mcp
What is the Test Intel MCP server?
Test Intel is an MCP server listed in the public MCP registry as io.github.barissozudogru/test-intel. Coverage analysis, untested function detection and complexity scoring for TS and JS. This page covers its npm package (@barissozudogru/test-intel-mcp).
Is the Test Intel MCP server safe to use?
Test Intel scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Test Intel MCP server expose?
Test Intel exposes 4 tools: analyze_test_coverage, find_untested_functions, get_function_complexity, suggest_test_cases. Their descriptions and schemas cost roughly 285 tokens of context every time the server is loaded.
Is the Test Intel MCP server still maintained?
Test Intel is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Test Intel MCP server under?
Test Intel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.