Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Test Intel

by barissozudogruversion 0.8.1i★ –iRuns on your computer
Registry nameio.github.barissozudogru/test-intel

Install

Overview

Description from the maker (original English)

Coverage analysis, untested function detection and complexity scoring for TS and JS.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@barissozudogru/test-intel-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add test-intel -- npx -y @barissozudogru/test-intel-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@barissozudogru/test-intel-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "test-intel": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@barissozudogru/test-intel-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account barissozudogru, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18326 servers in this category
  • Published to the registry more recently than 29% of the other 18326 servers in this category
  • Basic checks equal to or better than 100% of the other 18326 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Test Intel safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.8.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Signoff

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Signoff

by ayuanxx-max

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

test-intel-mcp

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 test-intel to analyze coverage/lcov.info, identify the highest-impact gaps,

and suggest tests for the most complex uncovered function.

No account, API key, or hosted service is required. File access is restricted to the directory where the server starts.

Proof on this repository

Running the complexity tool against the real src/paths.ts file produces:

Function complexity analysis for: src/paths.ts

Total functions analyzed: 1

Priority | Function | Line | Cyclomatic | Branches | Loops ---------|-----------------|------|------------|----------|------ low | deriveTestPaths | 11 | 3 | 1 | 1

Summary: 0 critical, 0 high, 0 medium, 1 low priority

The same server reads lcov, Istanbul JSON, and Cobertura files to surface uncovered functions, lines, and branches.

A pinned p-limit 7.3.1 case study reproduces coverage from the upstream project's 22 passing tests. test-intel-report reduces its lcov artifact to two uncovered lines and one uncovered branch while preserving the original coverage file for inspection.

If this saves you time, consider starring the repository. It helps other developers find it.

Tools

ToolWhat it answers
analyze_test_coverageWhich files, functions, lines, and branches remain uncovered?
find_untested_functionsWhich source functions have no corresponding test file?
get_function_complexityWhich functions deserve testing attention first?
suggest_test_casesWhich happy path, boundary, error, async, and type cases should be reviewed?

Supported coverage formats:

FormatCommon producers
lcovJest, Vitest, nyc, Istanbul
Istanbul JSONJest, nyc, Istanbul
Cobertura XMLJest, pytest-cov, JaCoCo

Heuristic source-to-test matching and complexity scores are prioritization signals. Native coverage data and human review remain the source of truth.

Coverage report command

The package also includes a non-MCP command for CI and terminal use:

npx -y -p @barissozudogru/test-intel-mcp test-intel-report coverage/lcov.info

An explicit format can be supplied when the filename is ambiguous:

test-intel-report coverage/result.xml cobertura

GitHub Action

Generate coverage with the project's own test runner, then pass the resulting artifact to the action:

name: Test priorities

on: [pull_request]

jobs: test-intel: runs-on: ubuntu-latest permissions: contents: read steps:

  • uses: actions/checkout@v4
  • name: Run tests with coverage run: npm ci && npm test -- --coverage
  • uses: barissozudogru/test-intel-mcp@v0.8.1 with: coverage-path: coverage/lcov.info

The report is written to the workflow summary. The action analyzes an artifact that already exists and does not upload source or coverage data.

Client setup

Claude Desktop, Cursor, Windsurf, Cline, and similar clients

Use the stdio configuration from the quickstart. Config file locations differ by client, but the server entry is the same:

{

"mcpServers": { "test-intel": { "command": "npx", "args": ["-y", "@barissozudogru/test-intel-mcp"] } } }

VS Code with Copilot

Create .vscode/mcp.json:

{

"servers": { "test-intel": { "type": "stdio", "command": "npx", "args": ["-y", "@barissozudogru/test-intel-mcp"] } } }

Streamable HTTP

Start the local endpoint:

npx @barissozudogru/test-intel-mcp --http

The MCP endpoint is http://localhost:3000/mcp and the health endpoint is http://localhost:3000/health. Set PORT to use another port.

Docker

docker build -t test-intel-mcp .

docker run -p 3000:3000 -v "$(pwd):/project" -w /project test-intel-mcp

Connect an HTTP client to http://localhost:3000/mcp.

Local development

npm install

npm test npm run build node dist/index.js

Requirements: Node.js 18 or newer.

See CONTRIBUTING.md for the development workflow.

Security and limits

  • Analysis runs locally and does not require network access.
  • Paths outside the server's starting directory are rejected.
  • Function discovery, source-to-test matching, and complexity scoring are heuristic.
  • A missing matching test filename does not prove a function is behaviorally untested.

License

MIT

Ask PopNx