OpsTruth Verification

MCP connector

Server URL

https://mcp.opstruth.io/mcpCopy

Login

None

Protocol

MCP 2025-11-25

Instructions

Use OpsTruth for evidence-first public GitHub and user-supplied HTTPS health checks. Inspect before broad audits and prefer the narrowest matching tool. Use signed Evidence Graph snapshots when repository, commit, CI and optional runtime observations must be bound to one subject; compare only compatible caller-held snapshots. Verify execution outcomes only from a complete request, authorisation and receipt chain with separate authoritative authorizer and executor fingerprint allowlists, and never infer success from the receipt state. For DoneState, attest only a sealed v2 handoff and return the signed result for separate submission; OpsTruth never calls DoneState or changes its run. Never ask for credentials, infer build success from static files or mutate the target. Use the render tool only after a data tool returns a final report.

Tools

Skills

6 in the ChatGPT listing

• Audit RepositoryUse this when a user needs live, read-only evidence about a public GitHub repository, from a quick map to a broad readiness audit, environment review, secret-risk scan, API review or migration review.
• Reconcile Agent ClaimsUse this when a user asks whether an AI or agent really finished a public-repository task, whether claims drift from live evidence, or which lowest-authority verification capability should run next.
• Review Change SafetyUse this before implementation, pull-request handoff, migration, deployment or publication when a user needs static safety evidence about visible API, environment, secret or deployment changes in a public GitHub repository.
• Trace ApplicationUse this when a user asks how a public GitHub application is wired, where requests enter, which routes or API surfaces exist, or which runtime claims repository evidence can support.
• Verify Action ReceiptUse this when a user supplies an AgentProof v2 receipt, OpsTruth evidence receipt, complete OpsTruth v1 execution handoff, or sealed DoneState v2 verification handoff and needs integrity, signer trust or fresh outcome verification.
• Verify Release ReadinessUse this when a user asks whether a public GitHub repository has visible CI, deployment, packaging or handoff evidence for a release.