Test Intel vs io.github.felixgeelhaar/coverctl
Test Intel is an MCP server published by barissozudogru. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.felixgeelhaar/coverctl is an MCP server published by felixgeelhaar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Test Intel |  io.github.felixgeelhaar/coverctl |
|---|---|---|
| Official MCP Registry | Listed Version: 0.8.1 Downloads/month (npm): 192 Downloads/week (npm): 52 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.16.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Test Intel | io.github.felixgeelhaar/coverctl |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barissozudogru/test-intel-mcp) | On your machine (https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-darwin-arm64.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/barissozudogru/test-intel-mcp | github.com/felixgeelhaar/coverctl |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Test Intel
Coverage analysis, untested function detection and complexity scoring for TS and JS.
io.github.felixgeelhaar/coverctl
Go code coverage analysis tool with MCP server for AI-powered coverage workflows
How to run each
Test Intel As a local MCP server: npm package
claude mcp add --transport stdio test-intel -- npx -y @barissozudogru/test-intel-mcpio.github.felixgeelhaar/coverctl
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Test Intel · What it can do: io.github.felixgeelhaar/coverctl · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.