Ext Ops Panel
Open dashboard
Comparison

bci vs io.github.farssaadeldin7-ux/haptic-feedback-mapper

bci is a plugin bundle for AI coding tools published by qinnovates. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.farssaadeldin7-ux/haptic-feedback-mapper is an MCP server published by farssaadeldin7-ux. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplacebciio.github.farssaadeldin7-ux/haptic-feedback-mapper
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
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

bci vs io.github.farssaadeldin7-ux/haptic-feedback-mapper
Factbciio.github.farssaadeldin7-ux/haptic-feedback-mapper
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/farssaadeldin7-ux/claude-plugin-suite/releases/download/mcpb-v0.1.3/haptic-feedback-mapper.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)12Not a bundle
Licence (differs)Apache-2.0 (code), CC-BY-4.0 (data)Not stated
Repository (differs)github.com/qinnovates/bci-securitygithub.com/farssaadeldin7-ux/claude-plugin-suite
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-20

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

bci

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

The first BCI toolkit for researchers, developers, and security engineers. Threat modeling, vulnerability scoring, pattern detection, and neuroethics compliance for brain-computer interfaces. Reports are built with privacy by design and auto-redact PII. Please see Github README before use.

io.github.farssaadeldin7-ux/haptic-feedback-mapper

In its own words, on Official MCP Registry:

Eliminates context-switching: quantifies the cognitive load of checking a screen, maps status...

How to run each

bci As a Claude Code plugin

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

io.github.farssaadeldin7-ux/haptic-feedback-mapper

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Neither one's marketplaces publish the settings it asks for.

What it can do: bci · What it can do: io.github.farssaadeldin7-ux/haptic-feedback-mapper · 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