Ext Ops Panel
Open dashboard
Comparison

decibel-peers vs io.github.telegraphprotocol/telegraph

decibel-peers is a plugin bundle for AI coding tools published by decibelsystems. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.telegraphprotocol/telegraph is an MCP server published by telegraphprotocol. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacedecibel-peersio.github.telegraphprotocol/telegraph
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 136
Downloads/week (npm): 43
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

decibel-peers vs io.github.telegraphprotocol/telegraph
Factdecibel-peersio.github.telegraphprotocol/telegraph
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (telegraph-protocol-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 2
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/decibelsystems/peersgithub.com/telegraphprotocol/telegraph-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

decibel-peers

In its own words, on Claude Code: claude-plugins-community:

Peer network patterns for Claude Code agent specialization. Peers gives Claude instances structured identity, discovery, messaging, and handoff protocols so specialist reviewers can coordinate cleanly across sessions

io.github.telegraphprotocol/telegraph

In its own words, on Official MCP Registry:

Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.

How to run each

decibel-peers As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install decibel-peers@claude-community

io.github.telegraphprotocol/telegraph As a local MCP server: npm package

Claude Code
claude mcp add --env "TELEGRAPH_DAEMON_URL=<YOUR_TELEGRAPH_DAEMON_URL>" --env "TELEGRAPH_ENGINE_URL=<YOUR_TELEGRAPH_ENGINE_URL>" --env "TELEGRAPH_EVM_PRIVATE_KEY=<YOUR_TELEGRAPH_EVM_PRIVATE_KEY>" --env "TELEGRAPH_NODE_URL=<YOUR_TELEGRAPH_NODE_URL>" --env "TELEGRAPH_SOLANA_PRIVATE_KEY=<YOUR_TELEGRAPH_SOLANA_PRIVATE_KEY>" --transport stdio telegraph -- npx -y telegraph-protocol-mcp

Requires: TELEGRAPH_DAEMON_URL, TELEGRAPH_ENGINE_URL, TELEGRAPH_EVM_PRIVATE_KEY (secret), TELEGRAPH_NODE_URL, TELEGRAPH_SOLANA_PRIVATE_KEY (secret)

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 decibel-peers publish no settings it asks for, so we do not compare settings.

What it can do: decibel-peers · What it can do: io.github.telegraphprotocol/telegraph · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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