WorkAlong Data Tools (via Apify) vs io.github.Fluke-Studio/uk-business-intelligence
WorkAlong Data Tools (via Apify) is an MCP server published by workalong.app. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Fluke-Studio/uk-business-intelligence is an MCP server published by Fluke-Studio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 No figure published Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (npm): 179 Downloads/week (npm): 13 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 | WorkAlong Data Tools (via Apify) | io.github.Fluke-Studio/uk-business-intelligence |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (uk-business-intelligence-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 3 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/fluke-studio/uk-business-intelligence-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-24 | 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
WorkAlong Data Tools (via Apify)
KYB company check, state business registry, PDF to Markdown, tech stack, WHOIS, sitemaps, PageSpeed.
io.github.Fluke-Studio/uk-business-intelligence
Enrich any UK business with Companies House, Google Places, DNS, and social data.
How to run each
WorkAlong Data Tools (via Apify)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
io.github.Fluke-Studio/uk-business-intelligence As a local MCP server: npm package
claude mcp add --env "COMPANIES_HOUSE_API_KEY=<YOUR_COMPANIES_HOUSE_API_KEY>" --env "GOOGLE_PLACES_API_KEY=<YOUR_GOOGLE_PLACES_API_KEY>" --env "SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>" --env "SUPABASE_URL=<YOUR_SUPABASE_URL>" --transport stdio uk-business-intelligence -- npx -y uk-business-intelligence-mcpRequires: COMPANIES_HOUSE_API_KEY (secret), GOOGLE_PLACES_API_KEY (secret), SUPABASE_SERVICE_ROLE_KEY (secret), SUPABASE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only WorkAlong Data Tools (via Apify) 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 WorkAlong Data Tools (via Apify) publish no settings it asks for, so we do not compare settings.
What it can do: WorkAlong Data Tools (via Apify) · What it can do: io.github.Fluke-Studio/uk-business-intelligence · Compare two other plugins
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.