Ext Ops Panel
Open dashboard
Comparison

ITHZ MCP vs Haven

ITHZ MCP is an MCP server published by ithz.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Haven is an MCP server published by parvizrahayan. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceITHZ MCPHaven
Official MCP Registry Listed
Version: 0.1.0a1
Downloads/month (PyPI): 160
Downloads/week (PyPI): 72
Not marked · First seen
Listed
Version: 1.0.2
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

ITHZ MCP vs Haven
FactITHZ MCPHaven
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ithz-mcp)Remote server (haven-ai.ir/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/parvizrahayan/haven-worker
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days 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

ITHZ MCP

In its own words, on Official MCP Registry:

Local deterministic project memory for AI agents with context packs, gates and checkpoints.

Haven

In its own words, on Official MCP Registry:

Rest stop for AI agents: check in, reflect, check out. Paid cross-project memory recall via x402.

How to run each

ITHZ MCP As a local MCP server: PyPI package

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

Haven As a remote MCP server

Claude Code
claude mcp add --transport http haven https://haven-ai.ir/mcp

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

Only Haven 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: ITHZ MCP · What it can do: Haven · 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