Ext Ops Panel
Open dashboard
Comparison

BrunoSan Intelligence Concierge vs Kultur.dev

BrunoSan Intelligence Concierge is an MCP server published by brunosan.de. Marketplaces we read that list it: 1 (Official MCP Registry). Kultur.dev is an MCP server published by kultur-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceBrunoSan Intelligence ConciergeKultur.dev
Official MCP Registry Listed
Version: 1.0.13
No figure published
Not marked · First seen
Listed
Version: 1.0.0
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

BrunoSan Intelligence Concierge vs Kultur.dev
FactBrunoSan Intelligence ConciergeKultur.dev
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (brunosan.de/mcp)Remote server (kultur.dev/api/mcp-sse/sse)
Transport (differs)Streamable HTTPSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/kultur-dev/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agoNot responding since 2026-10-14

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

BrunoSan Intelligence Concierge

In its own words, on Official MCP Registry:

Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints.

Kultur.dev

In its own words, on Official MCP Registry:

Cultural Intelligence Infrastructure for AI Agents — 200+ markets, 15 tones, 8 tools

How to run each

BrunoSan Intelligence Concierge As a remote MCP server

Claude Code
claude mcp add --transport http intelligence https://brunosan.de/mcp

Kultur.dev As a remote MCP server

Claude Code
claude mcp add --transport sse kultur-dev https://kultur.dev/api/mcp-sse/sse --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 the endpoint of BrunoSan Intelligence Concierge responded at the last daily 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: BrunoSan Intelligence Concierge · What it can do: Kultur.dev · 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.

Where the data comes from: how the catalog is built