Ext Ops Panel
Open dashboard
Comparison

Procurement Tools vs io.oxylabs/oxylabs-mcp

Procurement Tools is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.oxylabs/oxylabs-mcp is an MCP server published by oxylabs.io. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. 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
MarketplaceProcurement Toolsio.oxylabs/oxylabs-mcp
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 2.3.2
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.1
Downloads/month (PyPI): 4 016
Downloads/week (PyPI): 6 729
Forks (GitHub): 26
Stars (GitHub): 104
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:67085d076c5b
Forks (GitHub): 26
Pulls (Docker Hub): 39 545
Stars (Docker Hub): 3
Stars (GitHub): 104
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.10.0
Downloads/month (PyPI): 4 016
Downloads/week (PyPI): 6 729
Forks (GitHub): 26
Stars (GitHub): 104
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

Procurement Tools vs io.oxylabs/oxylabs-mcp
FactProcurement Toolsio.oxylabs/oxylabs-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)2 (worse)104 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub39 545
Forks (GitHub) (differs)0 (worse)26 (better)
Last release (differs)2026-10-22 (better)2026-10-15 (worse)
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published4
Environment variables it asks for (differs)Not published3, secrets among them: 3
Parts of the bundle (differs)55Not a bundle
LicenceMITMIT
Repository (differs)github.com/danielrosehill/procurement-tools-plugingithub.com/oxylabs/oxylabs-mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-26

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

Procurement Tools

In its own words, on Community GitHub marketplaces:

Product research and procurement skills with a particular focus on technical specification conformance — does this part actually meet the requirement, and can you show your working. Marketplace-agnostic: spec definition from a vague want or a photograph, annotated search vocabulary, versioned spec-as-code, manufacturer datasheet retrieval, cross-region part-number equivalence, conformance evaluation matrices, bills of materials and RFQ packages. Plus the surrounding process: intake, research, compare, evaluate, recommend, market-check, spec-driven market landscape surveys, live price/delivery scanning through your own VPN egress, preference memory and hardware-rig profiling. Hands off to the marketplace-specific plugins (shopping, israel-shopping, amazon, aliexpress-israel-skills) once a question becomes about a particular shop.

io.oxylabs/oxylabs-mcp

In its own words, on Official MCP Registry:

Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API.

How to run each

Procurement Tools As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install procurement-tools@danielrosehill

io.oxylabs/oxylabs-mcp As a remote MCP server

Claude Code
claude mcp add --transport http oxylabs-mcp https://mcp.oxylabs.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>" --header "X-Oxylabs-AI-Studio-Api-Key: <YOUR_X_OXYLABS_AI_STUDIO_API_KEY>"

Requires: OXYLABS_AI_STUDIO_API_KEY (secret), OXYLABS_PASSWORD (secret), OXYLABS_USERNAME (secret), Authorization header, X-Oxylabs-AI-Studio-Api-Key header

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

Only io.oxylabs/oxylabs-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Procurement Tools publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Procurement Tools publish no settings it asks for, so we do not compare settings.

What it can do: Procurement Tools · What it can do: io.oxylabs/oxylabs-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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.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