scope-check vs io.github.HarimxChoi/google-surf-mcp
scope-check is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
scope-check is a plugin bundle for AI coding tools published by Denis Darkin. No marketplace we read lists it any more. io.github.HarimxChoi/google-surf-mcp is an MCP server published by HarimxChoi. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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 |  io.github.HarimxChoi/google-surf-mcp | |
|---|---|---|
| Community marketplace dvdarkin/claude-skills | Removed on 2026-10-27 Version: 1.0.1 Forks (GitHub): 1 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.4 Downloads/month (npm): 1 729 Downloads/week (npm): 104 Forks (GitHub): 32 Stars (GitHub): 292 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.1.4 Downloads/month (npm): 1 729 Downloads/week (npm): 104 Forks (GitHub): 32 Stars (GitHub): 292 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 | scope-checkno longer listed · | io.github.HarimxChoi/google-surf-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 11 | 292 |
| Forks (GitHub) (differs) | 1 | 32 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (google-surf-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 29, secrets among them: 4 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/dvdarkin/claude-skills | github.com/harimxchoi/google-surf-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
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 scope-check
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) methodology. Use when users provide loose requirements…
-
Agentic Context Engineering: evolve context through bullets, deltas, and TF-IDF retrieval. Complete with schemas, validation, and production scripts.
-
Spec-driven development methodology with skills for requirements, design, tasks, AI prompting, QA, and troubleshooting
-
CodexQB packages adaptive evidence-backed repo planning, semantic validator gates, deterministic Goal previews, and artifact-based Step 4 apply orchestration.
-
Spec-Driven Development plugin for Claude Code and Cowork — a five-phase, spec-first workflow for planning and building software features. Includes Graphify integration.
-
A specification discovery plugin for Cowork and Claude Code. Helps product managers, founders, and tech leads figure out what to build before writing a single line of code. Unlike…
What each says it does
scope-check
Evaluates specification complexity against context window constraints. Automatically activates before writing design documents or implementation plans to prevent context budget overruns and mid-implementation context collapse.
io.github.HarimxChoi/google-surf-mcp
Web, academic and code search with graph RAG, data lineage, ontology and cross-project schema links.
How to run each
scope-check
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.HarimxChoi/google-surf-mcp As a local MCP server: npm package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --env "ORCAROUTER_API_KEY=<YOUR_ORCAROUTER_API_KEY>" --env "SEARCH_API=<YOUR_SEARCH_API>" --transport stdio google-surf-mcp -- npx -y google-surf-mcpRequires: ANTHROPIC_API_KEY (secret), GITHUB_TOKEN (secret), ORCAROUTER_API_KEY (secret), SEARCH_API (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 scope-check publish no settings it asks for, so we do not compare settings.
What it can do: scope-check · What it can do: io.github.HarimxChoi/google-surf-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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.