Weio Evidence Checks
OfficialRelated Servers
Alternatives to Weio Evidence Checks
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first production-readiness MCP server for AI-built apps. It runs read-only checks, produces an evidence-based readiness score, and guides fixes before launch.116Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local stdio MCP server that lets AI assistants run audits of generic HTML and Shopify product pages, gathering reproducible evidence on identity, structured data, images, links, specifications, and optional browser or link checks. It returns JSON and Markdown reports that the client can interpret, while keeping automated findings separate from checks requiring human judgment.MIT
- AlicenseAqualityAmaintenanceKeyless, local MCP server bringing ISTQB / OWASP / IEEE / ISO / EU AI Act QA standards into your AI client. Standards-grounded retrieval, deterministic QA effort estimation, automated QA document quality review (0-100 rubric), and JUnit/CSV test-results flakiness analysis.6789 PyPI7Apache 2.0
- AlicenseBqualityDmaintenanceA local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.33MIT

2ools MCP Serverofficial
AlicenseAqualityAmaintenanceRemote MCP server for 2ools—build, version, review, and export websites, web apps, and games from the AI chat you already use. This repository includes a credential-free stdio proxy and Dockerfile that forward introspection to the verified remote endpoint without mocking tools.431MIT- AlicenseAqualityAmaintenanceLocal stdio MCP server with six tools for browser verification detection, authorized provider test-key and owned image/text actions, and task resumption in an existing Playwright/CDP session. Includes four demos with server validation.66594 npm1MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of misselection or overlapping purpose. The tool's scope is clearly stated as closed-world consistency comparison of caller-supplied identifiers and digests.
The single tool name verify_production_provenance follows a consistent verb_noun pattern and is self-explanatory. No other tool names exist to create inconsistency.
A single tool is too thin for a server named 'Weio Evidence Checks', which suggests multiple evidence or provenance checks. The count feels under-scoped and leaves no room for related verification operations.
The tool only compares caller-supplied release identifiers and digests, explicitly excluding live observation, independent proof, authenticity verification, and production approval. For an evidence-checking server, this leaves significant gaps in lifecycle coverage and real verification capability.