Ext Ops Panel
Open dashboard
Comparison

io.github.meltingpixelsai/zero-core-tools vs io.github.ohad6k/emulo

io.github.meltingpixelsai/zero-core-tools is an MCP server published by meltingpixelsai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ohad6k/emulo is an MCP server published by ohad6k. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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.meltingpixelsai/zero-core-toolsio.github.ohad6k/emulo
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 81
Downloads/week (npm): 13
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.6.7
Downloads/month (PyPI): 713
Downloads/week (PyPI): 55
Forks (GitHub): 31
Stars (GitHub): 295
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.meltingpixelsai/zero-core-tools vs io.github.ohad6k/emulo
Factio.github.meltingpixelsai/zero-core-toolsio.github.ohad6k/emulo
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)295 (better)
Forks (GitHub) (differs)0 (worse)31 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (tools.rugslayer.com/mcp)On your machine (emulo)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/meltingpixelsai/harvey-toolsgithub.com/ohad6k/emulo
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 47 h agono remote endpoint we check

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.meltingpixelsai/zero-core-tools

In its own words, on Official MCP Registry:

Web scraping, code review, content gen, sentiment. Zero Core Tools.

io.github.ohad6k/emulo

In its own words, on Official MCP Registry:

Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.

How to run each

io.github.meltingpixelsai/zero-core-tools As a remote MCP server

Claude Code
claude mcp add --transport http zero-core-tools https://tools.rugslayer.com/mcp

io.github.ohad6k/emulo As a local MCP server: PyPI package

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

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

Only io.github.meltingpixelsai/zero-core-tools 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: io.github.meltingpixelsai/zero-core-tools · What it can do: io.github.ohad6k/emulo · 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