Ext Ops Panel
Open dashboard
Comparison

signalslabs vs UK Data: Sanctions screening

signalslabs is a plugin bundle for AI coding tools published by beee003. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). UK Data: Sanctions screening is an MCP server published by reliness.co.uk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplacesignalslabsUK Data: Sanctions screening
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.0
No figure published
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

signalslabs vs UK Data: Sanctions screening
FactsignalslabsUK Data: Sanctions screening
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (signalslabs-mcp)Remote server (ukdata.reliness.co.uk/mcp/sanctions-screening)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/beee003/signalslabs-mcpNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-06
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 44 h ago returned HTTP 500

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

signalslabs

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

AI-powered geopolitical intelligence. Get real-time signals, intelligence briefs, and event impact analysis for macro trading and risk assessment.

UK Data: Sanctions screening

In its own words, on Official MCP Registry:

Screen people, companies and ships against UK, US OFAC, EU and UN sanctions lists, daily

How to run each

signalslabs As a Claude Code plugin

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

UK Data: Sanctions screening As a remote MCP server

Claude Code
claude mcp add --transport http sanctions-screening https://ukdata.reliness.co.uk/mcp/sanctions-screening --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only UK Data: Sanctions 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

The marketplaces of UK Data: Sanctions screening publish no settings it asks for, so we do not compare settings.

What it can do: signalslabs · What it can do: UK Data: Sanctions screening · 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