Ext Ops Panel
Open dashboard
Comparison

BLEA vs io.github.aks129/healthclaw-guardrails

BLEA is an MCP server published by Nitmi. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). io.github.aks129/healthclaw-guardrails is an MCP server published by aks129. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-09. 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
MarketplaceBLEAio.github.aks129/healthclaw-guardrails
Official MCP Registry Listed
Version: 0.7.0
Downloads/month (PyPI): 423
Downloads/week (PyPI): 34
Forks (GitHub): 0
Stars (GitHub): 13
Not marked · First seen
Listed
Version: 1.6.0
Forks (GitHub): 12
Stars (GitHub): 33
Not marked · First seen
Copilot CLI: github/awesome-copilot Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 13
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 12
Stars (GitHub): 33
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

BLEA vs io.github.aks129/healthclaw-guardrails
FactBLEAio.github.aks129/healthclaw-guardrails
Marketplaces that list it22
Stars (GitHub) (differs)13 (worse)33 (better)
Forks (GitHub) (differs)0 (worse)12 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (blea)Remote server (mcp-server-production-5112.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)215
LicenceMITMIT
Repository (differs)github.com/nitmi/bleagithub.com/aks129/healthclawguardrails
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 15 h ago, requires authentication

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.

io.github.aks129/healthclaw-guardrails

In its own words, on Official MCP Registry:

Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation

How to run each

BLEA As a local MCP server: PyPI package

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

io.github.aks129/healthclaw-guardrails As a remote MCP server

Claude Code
claude mcp add --transport http healthclaw-guardrails https://mcp-server-production-5112.up.railway.app/mcp --header "X-Step-Up-Token: <YOUR_X_STEP_UP_TOKEN>"

Requires: X-Step-Up-Token header

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

Only io.github.aks129/healthclaw-guardrails 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: BLEA · What it can do: io.github.aks129/healthclaw-guardrails · 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. 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