Ext Ops Panel
Open dashboard
Comparison

Chip MCP vs io.github.keshrath/agent-tasks

Chip MCP is an MCP server published by chip-ai.digital. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-tasks is an MCP server published by keshrath. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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
MarketplaceChip MCPio.github.keshrath/agent-tasks
Official MCP Registry Listed
Version: 1.3.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.1.0
Downloads/month (npm): 842
Downloads/week (npm): 91
Forks (GitHub): 6
Stars (GitHub): 22
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.10.10
Forks (GitHub): 6
Stars (GitHub): 22
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

Chip MCP vs io.github.keshrath/agent-tasks
FactChip MCPio.github.keshrath/agent-tasks
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)22 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last release (differs)Not published2026-10-24
Where it runs (differs)Remote server (chip-ai.digital/mcp)On your machine (agent-tasks)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/zapret-digital/chip-mcpgithub.com/keshrath/agent-tasks
Changes in the last 7 days (differs)012
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 36 h ago, requires a keyno 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

Chip MCP

In its own words, on Official MCP Registry:

Project memory, tasks and Telegram notifications for your coding agent. Chip account required.

io.github.keshrath/agent-tasks

In its own words, on Official MCP Registry:

Pipeline task management for AI agents - stages, dependencies, artifacts, claiming

How to run each

Chip MCP As a remote MCP server

Claude Code
claude mcp add --transport http chip https://chip-ai.digital/mcp/

io.github.keshrath/agent-tasks As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-tasks -- npx -y agent-tasks

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

Only Chip MCP 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: Chip MCP · What it can do: io.github.keshrath/agent-tasks · 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