Ext Ops Panel
Open dashboard
Comparison

@brutalist/mcp vs io.github.jschoemaker/mcpgo

@brutalist/mcp is an MCP server published by @brutalist. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.jschoemaker/mcpgo is an MCP server published by jschoemaker. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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

Where each is published
Marketplace@brutalist/mcpio.github.jschoemaker/mcpgo
npm registry (MCP servers) Listed
Version: 1.18.10
Downloads/month (npm): 675
Downloads/week (npm): 135
Forks (GitHub): 5
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.6
Downloads/month (npm): 184
Downloads/week (npm): 23
Forks (GitHub): 0
Stars (GitHub): 0
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

@brutalist/mcp vs io.github.jschoemaker/mcpgo
Fact@brutalist/mcpio.github.jschoemaker/mcpgo
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)0 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@brutalist/mcp)On your machine (@exfil/mcpgo)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/ejmockler/brutalist-mcpgithub.com/jschoemaker/mcpgo
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

@brutalist/mcp

In its own words, on npm registry (MCP servers):

Deploy Claude Code, Codex & Antigravity (agy) CLI agents to demolish your work before users do. Real file analysis. Brutal honesty. Per-call model pinning, conversation continuation & intelligent pagination.

io.github.jschoemaker/mcpgo

In its own words, on Official MCP Registry:

Manage your Claude Code MCPs by talking to Claude — list, restart, wrap, and more.

How to run each

@brutalist/mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.jschoemaker/mcpgo As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcpgo -- npx -y @exfil/mcpgo

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: @brutalist/mcp · What it can do: io.github.jschoemaker/mcpgo · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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.

Where the data comes from: how the catalog is built