Ext Ops Panel
Open dashboard
Comparison

com.mudko/agent-ready-kit vs io.github.keshrath/agent-comm

com.mudko/agent-ready-kit is an MCP server published by mudko.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-comm 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-18. 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
Marketplacecom.mudko/agent-ready-kitio.github.keshrath/agent-comm
Official MCP Registry Listed
Version: 1.0.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.3.12
Downloads/month (npm): 1 084
Downloads/week (npm): 273
Forks (GitHub): 5
Stars (GitHub): 9
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.3.9
Forks (GitHub): 5
Stars (GitHub): 9
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

com.mudko/agent-ready-kit vs io.github.keshrath/agent-comm
Factcom.mudko/agent-ready-kitio.github.keshrath/agent-comm
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mudko.com/api/mcp)On your machine (agent-comm)
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/lmno100/mudkogithub.com/keshrath/agent-comm
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 36 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

com.mudko/agent-ready-kit

In its own words, on Official MCP Registry:

Agent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.

io.github.keshrath/agent-comm

In its own words, on Official MCP Registry:

Agent intercommunication - messaging, channels, shared state, and real-time events

How to run each

com.mudko/agent-ready-kit As a remote MCP server

Claude Code
claude mcp add --transport http agent-ready-kit https://mudko.com/api/mcp

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

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

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

Only com.mudko/agent-ready-kit 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: com.mudko/agent-ready-kit · What it can do: io.github.keshrath/agent-comm · 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