Ext Ops Panel
Open dashboard
Comparison

A2A Peptides vs BLEA

A2A Peptides is an MCP server published by A2A-Peptides. Marketplaces we read that list it: 1 (Official MCP Registry). BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). 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
MarketplaceA2A PeptidesBLEA
Official MCP Registry Listed
Version: 1.6.7
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.7.0
Downloads/month (PyPI): 423
Downloads/week (PyPI): 55
Forks (GitHub): 0
Stars (GitHub): 12
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 12
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

A2A Peptides vs BLEA
FactA2A PeptidesBLEA
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)12 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.a2a-peptides.ai/mcp)On your machine (blea)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Not statedMIT
Repository (differs)github.com/a2a-peptides/a2a-peptidesgithub.com/nitmi/blea
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days 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

A2A Peptides

In its own words, on Official MCP Registry:

Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for peptides.

BLEA

In its own words, on Official MCP Registry:

Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.

How to run each

A2A Peptides As a remote MCP server

Claude Code
claude mcp add --transport http a2a-peptides https://mcp.a2a-peptides.ai/mcp

BLEA As a local MCP server: PyPI package

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

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

Only A2A Peptides 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: A2A Peptides · What it can do: BLEA · 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/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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