Opzyai Pro vs opendrs
Opzyai Pro is an MCP server published by opzyai.com. Marketplaces we read that list it: 1 (Official MCP Registry). opendrs is an MCP server published by error-path. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  opendrs | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.5.2 Downloads/month (npm): 1 409 Downloads/week (npm): 114 Forks (GitHub): 0 Stars (GitHub): 3 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 | Opzyai Pro | opendrs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-12 |
| Where it runs (differs) | Remote server (www.opzyai.com/api/mcp/pro/mcp) | On your machine (@error-path/opendrs) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/error-path/opendrs |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | No HTTP response at the last check (21 h ago) | no remote endpoint we check |
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
Opzyai Pro
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
opendrs
PR blast radius and 0-1 risk score from git history, so low-risk PRs can be auto-approved.
How to run each
Opzyai Pro As a remote MCP server
claude mcp add --transport http pro https://www.opzyai.com/api/mcp/pro/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
opendrs As a local MCP server: npm package
claude mcp add --transport stdio opendrs -- npx -y @error-path/opendrs mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Opzyai Pro 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: Opzyai Pro · What it can do: opendrs · Compare two other plugins
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.