Ext Ops Panel
Open dashboard
Comparison

web-access vs com.dechonet/mcp

web-access is a plugin bundle for AI coding tools published by 一泽 Eze. Marketplaces we read that list it: 1 (Community GitHub marketplaces). com.dechonet/mcp is an MCP server published by dechonet.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. 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
Marketplaceweb-accesscom.dechonet/mcp
Community marketplace eze-is/web-access Listed
Version: 2.6.0
Forks (GitHub): 657
Stars (GitHub): 9 210
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.6.3
Downloads/month (npm): 2 992
Downloads/week (npm): 1 404
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.6.3
Downloads/month (npm): 2 992
Downloads/week (npm): 1 404
Forks (GitHub): 0
Stars (GitHub): 1
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

web-access vs com.dechonet/mcp
Factweb-accesscom.dechonet/mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 210 (better)1 (worse)
Forks (GitHub) (differs)657 (better)0 (worse)
Last release (differs)Not published2026-10-19
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
LicenceMITMIT
Repository (differs)github.com/eze-is/web-accessgithub.com/node-man/dechonet-mcp
Changes in the last 7 days (differs)220 or more
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 34 h ago

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

web-access

In its own words, on Community GitHub marketplaces:

All web operations: search, fetch, CDP browser automation, site experience accumulation

com.dechonet/mcp

In its own words, on Official MCP Registry:

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

How to run each

web-access As a Claude Code plugin

Claude Code
/plugin marketplace add eze-is/web-access
/plugin install web-access@web-access

com.dechonet/mcp As a remote MCP server

Claude Code
claude mcp add --transport http com-dechonet-mcp https://dechonet.com/mcp

Requires: DECHONET_API_KEY (secret), DECHONET_SESSION_COOKIE (secret)

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

Only com.dechonet/mcp has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of web-access nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: web-access · What it can do: com.dechonet/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