Ext Ops Panel
Open dashboard
Comparison

claude-connoisseur vs io.github.PhilflowIO/dav-mcp

claude-connoisseur is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.

claude-connoisseur is a plugin bundle for AI coding tools published by Eugenio Segala. No marketplace we read lists it any more. io.github.PhilflowIO/dav-mcp is an MCP server published by PhilflowIO. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-connoisseurio.github.PhilflowIO/dav-mcp
Community marketplace eugeniosegala/claude-connoisseur Removed on 2026-10-24
Version: 1.0.26
Forks (GitHub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 5.0.0
Downloads/month (npm): 2 406
Downloads/week (npm): 313
Forks (GitHub): 18
Stars (GitHub): 43
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 5.0.0
Downloads/month (npm): 2 406
Downloads/week (npm): 313
Forks (GitHub): 18
Stars (GitHub): 43
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

claude-connoisseur vs io.github.PhilflowIO/dav-mcp
Factclaude-connoisseurno longer listed · io.github.PhilflowIO/dav-mcp
Marketplaces that list it (differs)02
Stars (GitHub) (differs)943
Forks (GitHub) (differs)018
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (dav-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 3
Hooks it runs (differs)3Not published
Parts of the bundle (differs)16Not a bundle
LicenceMITMIT
Repository (differs)github.com/eugeniosegala/claude-connoisseurgithub.com/philflowio/dav-mcp
Changes in the last 7 days00
First seen (differs)2026-10-182026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of claude-connoisseur

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • claude-universe

    Five intelligence systems for Claude Code. Analyze instruction quality, generate deeper tests, scan for security vulnerabilities, understand codebase architecture, and trace how…

    by mbwsims · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-damn

    A SME of SWE: a plugin giving Claude Code the expertise of an Expert Software Engineer across every SWE area, while still inviting novice programmers to make gains on…

    by laurac8r · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-code-prompts

    Routes Claude Code tasks to focused prompts and adds deterministic documentation, skill, release, safety, and capability-audit workflows.

    by Rtur2003 · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-forge

    Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.

    by JunghyunRyu · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • everything-claude-code

    The most comprehensive Claude Code plugin — 36 agents, 142 skills, 68 legacy command shims, and production-ready hooks for TDD, security scanning, code review, and continuous…

    by Affaan Mustafa · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-deep-review

    A research-backed code review plugin for Claude Code that orchestrates parallel concern-specialized agents, cross-validates findings with deterministic verification, and produces…

    by liatrio-labs · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

claude-connoisseur

In its own words, on Community GitHub marketplaces:

A collection of skills, rules, hooks and more for Claude Code, curated with taste for good coding!

io.github.PhilflowIO/dav-mcp

In its own words, on Official MCP Registry:

AI-orchestrated calendars, contacts & tasks across any DAV platform. 27 tools, field-agnostic.

How to run each

claude-connoisseur

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

io.github.PhilflowIO/dav-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "CALDAV_PASSWORD=<YOUR_CALDAV_PASSWORD>" --env "CALDAV_SERVER_URL=<YOUR_CALDAV_SERVER_URL>" --env "CALDAV_USERNAME=<YOUR_CALDAV_USERNAME>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GOOGLE_REFRESH_TOKEN=<YOUR_GOOGLE_REFRESH_TOKEN>" --transport stdio dav-mcp -- npx -y dav-mcp

Requires: CALDAV_PASSWORD (secret), CALDAV_SERVER_URL, CALDAV_USERNAME, GOOGLE_CLIENT_SECRET (secret), GOOGLE_REFRESH_TOKEN (secret)

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

The marketplaces of claude-connoisseur publish no settings it asks for, so we do not compare settings.

What it can do: claude-connoisseur · What it can do: io.github.PhilflowIO/dav-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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