Ext Ops Panel
Open dashboard
Comparison

web-access vs TinyFish AI Web Agent

web-access is a plugin bundle for AI coding tools published by 一泽 Eze. Marketplaces we read that list it: 1 (Community GitHub marketplaces). TinyFish AI Web Agent is an MCP server published by agent.tinyfish.ai. Marketplaces we read that list it: 1 (Official MCP Registry). 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-accessTinyFish AI Web Agent
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.0.1
No figure published
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 TinyFish AI Web Agent
Factweb-accessTinyFish AI Web Agent
Marketplaces that list it11
Stars (GitHub) (differs)9 210No figure on GitHub
Forks (GitHub) (differs)657No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (agent.tinyfish.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/eze-is/web-accessNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

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

TinyFish AI Web Agent

In its own words, on Official MCP Registry:

AI-powered web automation. Navigate websites using AI agents for one page or a thousand

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

TinyFish AI Web Agent As a remote MCP server

Claude Code
claude mcp add --transport http web-agent https://agent.tinyfish.ai/mcp

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

Only TinyFish AI Web Agent 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: web-access · What it can do: TinyFish AI Web Agent · 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. 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