io.github.CloudCorpRecords/jpverify vs io.oxylabs/oxylabs-mcp
io.github.CloudCorpRecords/jpverify is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). 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-11-12. 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
| Marketplace |  io.github.CloudCorpRecords/jpverify |  io.oxylabs/oxylabs-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.10.2 Downloads/month (PyPI): 4 016 Downloads/week (PyPI): 15 062 Forks (GitHub): 27 Stars (GitHub): 105 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:67085d076c5b Forks (GitHub): 27 Pulls (Docker Hub): 39 860 Stars (Docker Hub): 3 Stars (GitHub): 105 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.10.2 Downloads/month (PyPI): 4 016 Downloads/week (PyPI): 15 062 Forks (GitHub): 27 Stars (GitHub): 105 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
| Fact | io.github.CloudCorpRecords/jpverify | io.oxylabs/oxylabs-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 105 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 39 860 |
| Forks (GitHub) (differs) | 0 (worse) | 27 (better) |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (@reneturcios/jpverify) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 4 |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 4 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cloudcorprecords/jpverify | github.com/oxylabs/oxylabs-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-10 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 9 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
io.github.CloudCorpRecords/jpverify
Verify Japanese companies: corporate numbers, invoice registrations, profiles and addresses.
io.oxylabs/oxylabs-mcp
Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API.
How to run each
io.github.CloudCorpRecords/jpverify As a local MCP server: npm package
claude mcp add --transport stdio jpverify -- npx -y @reneturcios/jpverify mcpio.oxylabs/oxylabs-mcp As a remote MCP server
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_API_TOKEN (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 io.github.CloudCorpRecords/jpverify publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.CloudCorpRecords/jpverify publish no settings it asks for, so we do not compare settings.
What it can do: io.github.CloudCorpRecords/jpverify · What it can do: io.oxylabs/oxylabs-mcp · Compare two other plugins
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.