slopsec vs VibeDoctor
slopsec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑03.
slopsec is a plugin bundle for AI coding tools published by Lachy. No marketplace we read lists it any more. VibeDoctor is an MCP server published by vibedoctor.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  VibeDoctor | |
|---|---|---|
| Community marketplace lachydotmcg/slopsec | Removed on 2026-11-03 Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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
| Fact | slopsecno longer listed · | VibeDoctor |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 25 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (vibedoctor.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/lachydotmcg/slopsec | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-26 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 27 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of slopsec
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Security auditor and hardener for vibe-coded projects. 170+ vulnerability checks across 24 categories including injection, XSS, auth bypass, IDOR, Supabase RLS, prompt injection…
-
Security vulnerability detection and remediation: OWASP Top 10 2025, SAST scanning, CVE research (NVD, OSV.dev), dependency audit, secrets detection, security headers, auth…
-
Comprehensive security scanner for vulnerabilities and OWASP Top 10 issues
-
Security auditor for Node.js and Python backend APIs. Four skills cover pre-audit reconnaissance (route graph, auth matrix, invariants), static code audit across the OWASP API…
-
Security best practices and vulnerability detection
-
Enterprise grade AI-native application security scanning, validation, and remediation
What each says it does
slopsec
Security audit for vibe-coded SaaS apps: 50 checks, severity scoring, prioritized fix list
VibeDoctor
Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes
How to run each
slopsec
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
VibeDoctor As a remote MCP server
claude mcp add --transport http vibedoctor https://vibedoctor.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only VibeDoctor 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: slopsec · What it can do: VibeDoctor · 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.