Ext Ops Panel
Open dashboard
Comparison

CliDeck MCP — Network Knowledge vs io.github.4DA-Systems/4da-mcp-server

CliDeck MCP — Network Knowledge is an MCP server published by clideck.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.4DA-Systems/4da-mcp-server is an MCP server published by 4DA-Systems. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceCliDeck MCP — Network Knowledgeio.github.4DA-Systems/4da-mcp-server
Official MCP Registry Listed
Version: 0.8.5
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 6.2.4
Downloads/month (npm): 2 373
Downloads/week (npm): 1 229
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

CliDeck MCP — Network Knowledge vs io.github.4DA-Systems/4da-mcp-server
FactCliDeck MCP — Network Knowledgeio.github.4DA-Systems/4da-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)2 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Remote server (mcp.clideck.com/mcp)On your machine (@4da/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/smartroot7/clideck-mcpgithub.com/4da-systems/4da-mcp-server
Changes in the last 7 days (differs)011
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agono 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

CliDeck MCP — Network Knowledge

In its own words, on Official MCP Registry:

Free verified network knowledge for AI agents: deterministic answers, honest unknowns.

io.github.4DA-Systems/4da-mcp-server

In its own words, on Official MCP Registry:

Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.

How to run each

CliDeck MCP — Network Knowledge As a remote MCP server

Claude Code
claude mcp add --transport http network-knowledge https://mcp.clideck.com/mcp

io.github.4DA-Systems/4da-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio 4da-mcp-server -- npx -y @4da/mcp-server

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

Only CliDeck MCP — Network Knowledge 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: CliDeck MCP — Network Knowledge · What it can do: io.github.4DA-Systems/4da-mcp-server · Compare two other plugins

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