ChatGPT Plugin

OpsTruth Verification

Verify coding work with proof

Brand: OpsTruth

Category: Developer Tools
Primary Subcategory: Test Automation & QA

Integration details

Description

OpsTruth Verification inspects public GitHub source and current CI evidence, traces static routes and configuration, and creates signed evidence snapshots. Explicitly supplied public HTTPS checks are bounded, with missing evidence and contradictions kept visible. It does not execute repository code, merge changes, deploy applications or accept private credentials.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Developer Tools
Primary Subcategory: Test Automation & QA
Secondary Subcategories: None listed
Brand: OpsTruth
Access: No account required
First tracked: 2026-10-23
Tool count: 21
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Test Automation & QA

View Category

Listed in alphabetical order

Primary Subcategory

Accessibility Checker WCAGComing soonGet notified

Accessibility RepairComing soonGet notified

AfterwardComing soonGet notified

BrowserStackComing soonGet notified

Cobalt CaptureComing soonGet notified

OpsTruth VerificationComing soonGet notified

Tools

21 tools agents can invoke

Use this only with a sealed DoneState verification handoff v2. OpsTruth validates its digest and exact subject, freshly reads the public GitHub commit, evaluates every sealed machine-checkable requirement, and returns a signed attestation for separate submission to DoneState. It never trusts executor success, submits the attestation, or changes the repository.
opstruth_attest_donestate_handoff
Use this to list visible environment variable names, configuration paths and package scripts. Environment values and secret-file contents are never read; do not request credentials through this tool.
opstruth_audit_environment
Use this for a broad, read-only evidence audit of a public GitHub repository, including readiness questions. Prefer a narrower tool for one concern. Never use it to modify, deploy or execute the repository.
opstruth_audit_repository
Use this for a bounded public-source scan of selected secret-like patterns. It returns only redacted types and locations, never values. It is not a complete history or credential-validity scan.
opstruth_audit_secrets
Use this when release confidence depends on current public GitHub Actions, check runs, commit status, branch protection or handoff files. It is read-only and cannot approve, merge, push or change GitHub.
opstruth_check_github_handoff
Use this for a static deployment preflight based on visible configuration and package scripts. It does not build, deploy, call provider APIs or prove live health.
opstruth_check_deployment
Use this to compare two caller-held OpsTruth Evidence Graph v1 snapshots. It checks graph integrity, signer trust and subject compatibility before reporting deterministic node, edge, contradiction and verdict changes. It performs no network request and stores nothing.
opstruth_compare_snapshots
Use this when you are unsure which read-only OpsTruth capability fits a concrete coding outcome. It recommends one bounded capability only and does not invoke tools, modify repositories or authorise actions.
opstruth_discover_capabilities
Use this before creating a DoneState objective that requires terminal independent verification. It returns only OpsTruth's configured public Ed25519 identity and compatible fingerprints, never a private key, trust decision or verification result.
opstruth_get_verifier_identity
Use this when you need a quick evidence map of a public GitHub repository before planning changes. It returns identity, structure, manifests, workflows, tests and proof gaps without executing code. Do not use it to inspect private repositories or claim a build passed.
opstruth_inspect_repository
Use this to create a bounded verification sequence with checkpoints and approval gates for a coding objective. It plans only; it does not execute, approve, deploy, merge or authorise actions.
opstruth_plan_workflow
Use this when the user needs a plan to verify a repository build or tests in a separately connected isolated runner. It only prepares an approval-gated handoff from declared scripts and never executes code, installs dependencies or accepts credentials.
opstruth_prepare_sandbox_verification
Use this only when the user supplies a public HTTPS deployment URL and asks for a bounded health check. It retains status and headers but no response body; it rejects credentials, localhost, IP literals and non-HTTPS URLs. It does not deploy or diagnose private provider state.
opstruth_probe_deployment
Use this only after another OpsTruth data tool returned a report that should be presented as an interactive evidence summary. It does not fetch new evidence, execute code or change the supplied report.
opstruth_render_evidence
Use this to inventory visible API handlers and OpenAPI, GraphQL, schema or contract paths. It does not call, mutate or validate a deployed API and cannot prove consumer compatibility.
opstruth_review_api_contracts
Use this to review visible migration files and static risk indicators before a database change. It never connects to or changes a database and cannot prove applied state or rollback safety.
opstruth_review_migrations
Use this to bind public repository, current CI and optional explicitly supplied public HTTPS runtime observations into one portable signed Evidence Graph. It never executes repository code, stores the graph or claims that a reachable endpoint proves which commit is deployed.
opstruth_snapshot_evidence
Use this when you need statically visible page, API or declared route patterns in a public GitHub repository. It cannot prove live reachability, authentication, middleware behaviour or runtime correctness.
opstruth_trace_routes
Use this when an AgentProof signed receipt v2 is supplied and its structure, digest, signature or signer trust needs checking. It never executes or repeats the underlying action and does not infer that a valid receipt proves the action was safe.
opstruth_verify_receipt
Use this when an OpsTruth evidence report receipt is supplied and its digest, Ed25519 signature or signer trust needs independent checking. It never repeats the inspection or probe and does not turn evidence into a deployment approval.
opstruth_verify_evidence_receipt
Use this after a separately authorised executor returns a signed receipt. OpsTruth validates the request, authorisation and receipt chain against separate authorizer and executor fingerprint allowlists, enforces signer-role separation, freshly re-observes public repository, CI and optional HTTPS evidence, then signs an independent VerificationResult. Executor success alone can never produce VERIFIED.
opstruth_verify_execution_result

FAQs

OpsTruth Verification ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve OpsTruth Verification's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are OpsTruth Verification alternatives on ChatGPT?

As of 2026-10-23, OpsTruth Verification competes with Accessibility Checker WCAG, Accessibility Repair, Afterward, BrowserStack, Cobalt Capture, CodSpeed, Currents, Greptile and 14 more in ChatGPT Test Automation & QA, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.