AWS Bedrock Data Automation vs eterdis-vrio
eterdis-vrio is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). eterdis-vrio is a plugin bundle for AI coding tools published by Eterdis AS. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-26. 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 |  AWS Bedrock Data Automation | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 830 Pulls (Docker Hub): 14 647 Stars (Docker Hub): 0 Stars (GitHub): 9 835 Not marked · First seen |
Not listed |
| Community marketplace eterdis/strategy-skills | Not listed | Removed on 2026-10-26 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 10 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 | AWS Bedrock Data Automation | eterdis-vriono longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 9 835 | 10 |
| Pulls (Docker Hub) (differs) | 14 647 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 830 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | CC-BY-4.0 |
| Repository (differs) | github.com/awslabs/mcp | github.com/eterdis/strategy-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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 eterdis-vrio
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Product strategy skills: find-your-moat front door, 6-step strategy framework, competitive analysis, VRIO, strategic moats, ecosystem strategy, pre-mortem risk analysis…
-
Strategic Thinking Agent — meta-router for 47 business strategy frameworks (Porter Five Forces, Drucker MBO/5Q, Balanced Scorecard, Blue Ocean, Wardley Mapping, BCG Matrix, BMC…
-
DevsForge Enterprise Strategic Planning Architect delivering comprehensive business strategy development methodologies, implementation roadmap optimization, and competitive…
-
Open strategy frameworks for AI agents — 11 skills that turn any LLM into a strategy thinking partner. Each skill is a structured SKILL.md prompt that guides the AI through a…
-
12 executable skills + orchestrator for competitive strategy analysis, extracted from Michael Porter's Competitive Strategy. Five forces, competitor profiling, strategic groups…
-
Institutional-grade Business Analysis skills for Claude. Methodology-grade outputs grounded in BABOK and real delivery experience. Includes four plugins: Capability Mapping (MECE…
What each says it does
AWS Bedrock Data Automation
Analyze documents, images, videos, and audio.
eterdis-vrio
VRIO resource analysis combined with Dynamic Capabilities assessment — test whether your advantages are real and durable.
How to run each
AWS Bedrock Data Automation As a local MCP server: Docker image
claude mcp add --transport stdio aws-bedrock-data-automation -- docker run -i --rm mcp/aws-bedrock-data-automation-mcp-servereterdis-vrio
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of eterdis-vrio publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of eterdis-vrio publish no settings it asks for, so we do not compare settings.
What it can do: AWS Bedrock Data Automation · What it can do: eterdis-vrio · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.