Tools & modules

Operationalize the evidence

Verification is free and offline, in every runtime. Issuance and signing live behind the licensed issuer path (pilot / staging). Official status stays separate — no phone-home, no kill switch for free verification.

One signer, many verifier cores

TSP is one signer and N verifiers. The non-JS SDKs are verifier cores — they re-run the cryptography; they do not sign. Signing and issuance is the single licensed path.

@trust-standard-protocol/sdk-js

signer + verifier

the single issuance/signing path

@trust-standard-protocol/sdk-web

verifier core

browser-safe, verify-only

@trust-standard-protocol/sdk-python

verifier core

@trust-standard-protocol/sdk-go

verifier core

@trust-standard-protocol/sdk-rust

verifier core

@trust-standard-protocol/sdk-java

verifier core

@trust-standard-protocol/sdk-csharp

verifier core

npm i @trust-standard-protocol/sdk-web
import { verifyTrustEnvelopeV3 } from "@trust-standard-protocol/sdk-web";

Open MCP server & proxy

An open Model Context Protocol server and proxy let agents capture tool-call receipts and re-run verification inline. Distributed free with the verifier cores — the open layer of the protocol; the governed Seal is the product.

# verify a receipt from an agent loop, offline
tsp-mcp --proxy   # captures tool-call evidence; re-runs verification

Operator modules

Modules ship inactive; an offline license token activates them. Free verification always works.

Evidence Explorer

Search and filter receipts across a workflow.

Audit Dossier

Package receipts, reviews and manifests into one exportable bundle.

Risk Monitor

Flag missing evidence and stale keys — alerts, not a safety verdict.

Oversight Workflow

Review, escalate and override — every step signed.

Control Plane

Tenants, licenses, issuers and audit trail — no official status by payment.

Agent Gateway

Tool-call receipts and policy state — captures, never claims correctness.

TrustBadge — the evidence entry point

A drop-in component that links an AI output to its provenance receipt. The resolver decides whether official wording is allowed; the badge itself only ever reflects verification state.

See a TrustBadge react to live verification →

Security posture

· Report to security@truststandardprotocol.com — coordinated handling, no legal threat for good-faith research.
· Separate dev / staging / production keys. Rotation and revocation tested before launch. No production keys in public repos.
· No phone-home for self-hosted verification · no hidden telemetry · no remote kill switch for free verification.

Open layer: spec, fixtures, verifier cores and the TrustBadge component are source-available and citable (Apache-2.0). The closed Seal — issuance tooling and commercial modules — is under a commercial TSP license. Marks (TSP, Trust Standard Protocol, TrustEnvelope, TrustBadge) are controlled.

Full security posture and disclosure →