Ext Ops Panel
Open dashboard
Comparison

BLEA vs send0

BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). send0 is an MCP server published by send0-dev. 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
MarketplaceBLEAsend0
Official MCP Registry Listed
Version: 0.7.0
Downloads/month (PyPI): 423
Downloads/week (PyPI): 51
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Copilot CLI: github/awesome-copilot Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Not listed

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

BLEA vs send0
FactBLEAsend0
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)11 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (blea)Remote server (api.send0.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nitmi/bleagithub.com/send0-dev/send0-v2
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

BLEA

In its own words, on Official MCP Registry:

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

send0

In its own words, on Official MCP Registry:

Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.

How to run each

BLEA As a local MCP server: PyPI package

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

send0 As a remote MCP server

Claude Code
claude mcp add --transport http send0 https://api.send0.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

Requires: SEND0_API_KEY (secret), Authorization header

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

What it can do: BLEA · What it can do: send0 · 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