AWS Bedrock Data Automation vs Document Integrity Validator
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Document Integrity Validator is an MCP server published by OjasKord. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  AWS Bedrock Data Automation |  Document Integrity Validator |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 835 Pulls (Docker Hub): 14 677 Stars (Docker Hub): 0 Stars (GitHub): 9 839 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.20 Downloads/month (npm): 271 Downloads/week (npm): 56 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
| Fact | AWS Bedrock Data Automation | Document Integrity Validator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 839 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 14 677 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 835 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | Remote server (document-integrity-validator-mcp-production.up.railway.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/ojaskord/document-integrity-validator-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (3 days ago) |
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
AWS Bedrock Data Automation
Analyze documents, images, videos, and audio.
Document Integrity Validator
AI reasoning checks any document against known international standards before your agent acts on it.
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-serverDocument Integrity Validator As a remote MCP server
claude mcp add --transport http document-integrity-validator-mcp https://document-integrity-validator-mcp-production.up.railway.app/mcpRequires: ANTHROPIC_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Document Integrity Validator has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Document Integrity Validator publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Bedrock Data Automation asks for
AWS_BUCKET_NAMEAWS_PROFILEAWS_REGION
Only Document Integrity Validator asks for
ANTHROPIC_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Bedrock Data Automation · What it can do: Document Integrity Validator · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.