Ext Ops Panel
Open dashboard
Comparison

mdbrain vs io.brainfile/brainfile

mdbrain is a plugin bundle for AI coding tools published by chanjoongx. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.brainfile/brainfile is an MCP server published by brainfile.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacemdbrainio.brainfile/brainfile
Claude Code: claude-plugins-community Listed
Version: 0.4.6
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
No figure published
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

mdbrain vs io.brainfile/brainfile
Factmdbrainio.brainfile/brainfile
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (brainfile.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/chanjoongx/mdbrainNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 14 h ago

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

mdbrain

In its own words, on Claude Code: claude-plugins-community:

A native Claude Code extension that prevents AI from over-refactoring your intentional code. Combines XML-structured protocols (BRAIN/CRAFT/PERF) with a 16-entry false-positive catalog, enforced by a five-layer Safety Net: permissions deny list, PreToolUse hook, tool-scoped subagents, path-scoped rules, and behavioral protocols. Coexists non-destructively with existing CLAUDE.md and memory/.

io.brainfile/brainfile

In its own words, on Official MCP Registry:

Brainfile memory layer for Claude Code over MCP: free starter files + weekly freshness feed.

How to run each

mdbrain As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mdbrain@claude-community

io.brainfile/brainfile As a remote MCP server

Claude Code
claude mcp add --transport http brainfile https://brainfile.io/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.brainfile/brainfile has a remote endpoint we check. How we check endpoints

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: mdbrain · What it can do: io.brainfile/brainfile · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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