Connectors / Cloud, data & infrastructure

ProdVerity

Verify production releases

ProdVerity is a read-only production verification plugin for developers and operators. It checks whether a public HTTPS web app is reachable, inspects common security headers, discovers an optional ProdVerity verification manifest, runs deterministic public health checks, and can compare a public build marker with an expected commit or release identifier.

What you can ask

Verify whether https://greatskillsacademy.com is serving its declared production release.
Example path

MCP connector

Server URL: https://greatskillsacademy.com/prodverity/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: ProdVerity performs read-only production checks on public HTTPS web applications. Use it to distinguish deployment evidence from assumptions. It never authenticates to, mutates, deploys, or administers the target application. A basic reachability check is not proof of a specific release. Strong production verification requires a /.well-known/prodverity.json manifest and, when requested, a matching public build revision marker. Vision tools accept caller-supplied public HTTPS targets; GSA is a backward-compatible target, not a privileged scope. Raw captures remain evidence only; a PASS requires deterministic browser/DOM/reference evidence bound to the requested target. PDF ingestion accepts bounded caller-provided PDF bytes, validates MIME/header, computes SHA-256, and preserves explicit provenance. It never reads arbitrary server filesystem paths. Evidence marked INTERNAL_ASSET comes from a local resource binding, not the visitor-facing HTTP route. Do not report it as independent public production verification. Only PUBLIC_HTTP represents an outbound public HTTP observation; it is still not a browser check.

Tools

Reads data24

Skills

None in the store listings or on the server

MCP connector

Server URL

https://greatskillsacademy.com/prodverity/mcp

None

Protocol

MCP 2026-07-28

Instructions

ProdVerity performs read-only production checks on public HTTPS web applications. Use it to distinguish deployment evidence from assumptions. It never authenticates to, mutates, deploys, or administers the target application. A basic reachability check is not proof of a specific release. Strong production verification requires a /.well-known/prodverity.json manifest and, when requested, a matching public build revision marker. Vision tools accept caller-supplied public HTTPS targets; GSA is a backward-compatible target, not a privileged scope. Raw captures remain evidence only; a PASS requires deterministic browser/DOM/reference evidence bound to the requested target. PDF ingestion accepts bounded caller-provided PDF bytes, validates MIME/header, computes SHA-256, and preserves explicit provenance. It never reads arbitrary server filesystem paths. Evidence marked INTERNAL_ASSET comes from a local resource binding, not the visitor-facing HTTP route. Do not report it as independent public production verification. Only PUBLIC_HTTP represents an outbound public HTTP observation; it is still not a browser check.

Tools