Ext Ops Panel
Open dashboard
Comparison

Sipcode vs codexwatch

Sipcode is an MCP server published by Anuj7411. Marketplaces we read that list it: 1 (Official MCP Registry). codexwatch is an MCP server published by psychofict. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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
MarketplaceSipcodecodexwatch
Official MCP Registry Listed
Version: 1.7.1
Downloads/month (npm): 1 469
Downloads/week (npm): 256
Forks (GitHub): 4
Stars (GitHub): 46
Not marked · First seen
Listed
Version: 1.0.2
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

Sipcode vs codexwatch
FactSipcodecodexwatch
Marketplaces that list it11
Stars (GitHub) (differs)46 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)2026-10-12 (worse)2026-11-05 (better)
Where it runs (differs)On your machine (sipcode)On your machine (codexwatch-cli)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/anuj7411/sipcodegithub.com/psychofict/codexwatch
Changes in the last 7 days (differs)20
First seen (differs)2026-10-112026-11-04

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

Sipcode

In its own words, on Official MCP Registry:

Context hygiene for Claude Code: drift detection, re-read dedup, and token analytics.

codexwatch

In its own words, on Official MCP Registry:

OpenAI Codex usage from your local logs: tokens, API-equivalent cost and plan limits.

How to run each

Sipcode As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio sipcode -- npx -y -p sipcode sipcode sipcode-mcp

codexwatch As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio codexwatch -- uvx codexwatch-cli mcp

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: Sipcode · What it can do: codexwatch · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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