Ext Ops Panel
Open dashboard
Comparison

io.github.rog0x/file vs io.github.roshunsunder/filesift

io.github.rog0x/file is an MCP server published by rog0x. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.roshunsunder/filesift is an MCP server published by roshunsunder. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplaceio.github.rog0x/fileio.github.roshunsunder/filesift
Official MCP Registry Listed
Version: 1.0.1
Downloads/month (npm): 150
Downloads/week (npm): 27
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (PyPI): 61
Downloads/week (PyPI): 20
Forks (GitHub): 0
Stars (GitHub): 6
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

io.github.rog0x/file vs io.github.roshunsunder/filesift
Factio.github.rog0x/fileio.github.roshunsunder/filesift
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)6 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@rog0x/mcp-file-tools)On your machine (filesift)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/rog0x/mcp-file-toolsgithub.com/roshunsunder/filesift
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.rog0x/file

In its own words, on Official MCP Registry:

Dir tree, file stats, duplicates, LOC for AI agents

io.github.roshunsunder/filesift

In its own words, on Official MCP Registry:

Local file search for AI agents — semantic + keyword indexing over your codebase.

How to run each

io.github.rog0x/file As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio file -- npx -y @rog0x/mcp-file-tools

io.github.roshunsunder/filesift As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio filesift -- uvx filesift

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: io.github.rog0x/file · What it can do: io.github.roshunsunder/filesift · 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.

Where the data comes from: how the catalog is built