Ext Ops Panel
Open dashboard
Comparison

langguard-scope-mcp vs dev.getstub/check

langguard-scope-mcp is a plugin bundle for AI coding tools published by LangGuard-AI. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). dev.getstub/check is an MCP server published by getstub.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacelangguard-scope-mcpdev.getstub/check
Claude Code: claude-plugins-community Listed
Version: 0.17.0
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 216
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
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

langguard-scope-mcp vs dev.getstub/check
Factlangguard-scope-mcpdev.getstub/check
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (scope-mcp.langguard.ai/mcp)On your machine (@getstub/mcp-check)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)4Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/langguard-ai/scope-mcpgithub.com/getstub/recipes
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 33 h ago, requires a keyno 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

langguard-scope-mcp

In its own words, on Claude Code: claude-plugins-community:

SCOPE - Security, Compliance & Operational Policy Evaluation - A Claude plugin that runs deterministic pre-flight compliance evaluation on agentic workflows. Maps every MCP tool to risk level, business impact, and 25 regulatory regimes like SOC 2, GDPR, HIPAA, PCI, SOX, the EU AI Act — before the agent ships.

dev.getstub/check

In its own words, on Official MCP Registry:

Verify what an AI agent did for someone, and what commercial influence the operator disclosed.

How to run each

langguard-scope-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install langguard-scope-mcp@claude-community

dev.getstub/check As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio check -- npx -y @getstub/mcp-check

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

Only langguard-scope-mcp 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

The marketplaces of langguard-scope-mcp publish no settings it asks for, so we do not compare settings.

What it can do: langguard-scope-mcp · What it can do: dev.getstub/check · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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