com.compliapi/screening vs BLEA
com.compliapi/screening is an MCP server published by compliapi.com. 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-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
| Marketplace |  BLEA | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.7.0 Downloads/month (PyPI): 423 Downloads/week (PyPI): 51 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 0.6.1 Forks (GitHub): 0 Stars (GitHub): 11 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
| Fact | com.compliapi/screening | BLEA |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 11 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.compliapi.com/mcp) | On your machine (blea) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/nitmi/blea |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 h ago | no 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
com.compliapi/screening
OFAC and global sanctions screening: crypto addresses, emails, websites, IDs, countries, VPN, geo
BLEA
Safe BLE diagnostics, evidence workflows, and guarded automation for AI agents.
How to run each
com.compliapi/screening As a remote MCP server
claude mcp add --transport http screening https://api.compliapi.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
BLEA As a local MCP server: PyPI package
claude mcp add --transport stdio blea -- uvx blea mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.compliapi/screening 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: com.compliapi/screening · 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.