Ext Ops Panel
Open dashboard
Comparison

baizhi-agent-toolkit vs Mat Web & Data Toolkit (x402, Cloudflare)

baizhi-agent-toolkit is a plugin bundle for AI coding tools published by ct-jaryn. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Mat Web & Data Toolkit (x402, Cloudflare) is an MCP server published by automatom.matt-d59.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplacebaizhi-agent-toolkitMat Web & Data Toolkit (x402, Cloudflare)
Community marketplace davepoon/buildwithclaude Listed
Version: 0.1.0
Forks (GitHub): 653
Stars (GitHub): 3 680
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.6.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

baizhi-agent-toolkit vs Mat Web & Data Toolkit (x402, Cloudflare)
Factbaizhi-agent-toolkitMat Web & Data Toolkit (x402, Cloudflare)
Marketplaces that list it11
Stars (GitHub) (differs)3 680No figure on GitHub
Forks (GitHub) (differs)653No figure on GitHub
Last release (differs)Not published2026-10-18
Where it runs (differs)Remote server (agent-toolkit.app.baizhi.cloud/mcp)Remote server (automatom.matt-d59.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/davepoon/buildwithclaudeNot stated
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-17
Endpoint at the last check (differs)Responded 7 days agoResponded 4 days 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

baizhi-agent-toolkit

In its own words, on Community GitHub marketplaces:

Connect Baizhi Agent Toolkit through an authenticated remote MCP server, with an optional skill for bounded research and source verification. Requires a Baizhi account and API key; service usage may incur charges.

Mat Web & Data Toolkit (x402, Cloudflare)

In its own words, on Official MCP Registry:

x402 web/data toolkit: tools, US$5 lead pack, free flapjax_check, paid Nostr relay

How to run each

baizhi-agent-toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install baizhi-agent-toolkit@buildwithclaude

Mat Web & Data Toolkit (x402, Cloudflare) As a remote MCP server

Claude Code
claude mcp add --transport http web-data-toolkit https://automatom.matt-d59.workers.dev/mcp

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of baizhi-agent-toolkit nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: baizhi-agent-toolkit · What it can do: Mat Web & Data Toolkit (x402, Cloudflare) · 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