Ext Ops Panel
Open dashboard
Comparison

io.github.SirinivasK/chron vs macOS-only MCP server that exposes iMessage chat

io.github.SirinivasK/chron is an MCP server published by SirinivasK. Marketplaces we read that list it: 1 (Official MCP Registry). macOS-only MCP server that exposes iMessage chat is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-10. 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.SirinivasK/chronmacOS-only MCP server that exposes iMessage chat
Official MCP Registry Listed
Version: 0.1.7
Downloads/month (npm): 1 824
Downloads/week (npm): 753
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 2
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.SirinivasK/chron vs macOS-only MCP server that exposes iMessage chat
Factio.github.SirinivasK/chronmacOS-only MCP server that exposes iMessage chat
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)On your machine (chron-mcp)On your machine (https://github.com/adelaidasofia/imessage-mcp/releases/download/v0.1.0/imessage-mcp.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
LicenceNot statedNot stated
Repository (differs)github.com/nivaya/chrongithub.com/adelaidasofia/imessage-mcp
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.SirinivasK/chron

In its own words, on Official MCP Registry:

Timestamped audit log for every AI conversation — stored locally in SQLite, owned by you.

macOS-only MCP server that exposes iMessage chat

In its own words, on Official MCP Registry:

macOS-only MCP server that exposes iMessage chat.db to Claude and exports per-chat history to an…

How to run each

io.github.SirinivasK/chron As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio chron -- npx -y chron-mcp

macOS-only MCP server that exposes iMessage chat As a Claude Code plugin

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

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

The marketplaces of macOS-only MCP server that exposes iMessage chat publish no settings it asks for, so we do not compare settings.

What it can do: io.github.SirinivasK/chron · What it can do: macOS-only MCP server that exposes iMessage chat · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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