WINDI MCP Connector

Cryptographic proof that a human approved an AI decision

What is WINDI?

WINDI is a proof layer that records cryptographic evidence of a declared human decision, prior to the governed action — without ever touching your data.

The file never leaves your computer. WINDI only records the fingerprint (SHA-256 hash). Anyone can verify, no account needed.

WINDI is a witness, not a judge. It proves that something existed at a specific moment — it does NOT prove that the content is true, original, or legally valid.

Available Tools

windi_verify_digest READ
Check whether a SHA-256 digest has been sealed by WINDI. Returns VERIFIABLE or NOT_VERIFIABLE.

Important: NOT_VERIFIABLE means no record exists — it does NOT mean the content is fake.
windi_get_receipt READ
Retrieve a WINDI receipt by its ID. Returns receipt details including timestamp, actor, and verification URL.
windi_explain_scope READ
Return WINDI's statement of what a seal proves and does not prove. Call this when asked about WINDI's capabilities.

Note: Report the returned text rather than paraphrasing.

How to Connect

1
Open Claude Settings
Go to Settings → Connectors in Claude.ai or Claude Desktop
2
Add Custom Connector
Click "Add Connector" and enter:
https://windi-domain.com/mcp/
3
Authorize
You'll be redirected to WINDI to login with your DID (identity). If you don't have one, you can create it at windi-domain.com/verify-public/
4
Start Using
Ask Claude to verify a document hash or explain what WINDI proves.

Example Prompts

Example 1: Verify a document

You: "I have a document with SHA-256 hash a1b2c3d4e5f6.... Can you check if it's been sealed by WINDI?"

Claude will: Call windi_verify_digest with the hash and report whether it's VERIFIABLE or NOT_VERIFIABLE.

Example 2: Get receipt details

You: "Look up WINDI receipt WINDI-SEAL-20260915-ABCD1234"

Claude will: Call windi_get_receipt and return the timestamp, actor, document name, and verification URL.

Example 3: Understand WINDI's scope

You: "What exactly does a WINDI seal prove? And what doesn't it prove?"

Claude will: Call windi_explain_scope and report WINDI's official statement verbatim.

Example 4: Verify before signing

You: "Before I sign this contract, can you verify if the current version has been sealed?"

Claude will: Ask you for the SHA-256 hash of the document, then verify it against WINDI's ledger.

What WINDI Proves (and Doesn't)

Scope Statement

WINDI PROVES:

  • That a specific SHA-256 digest was registered at a specific moment
  • That a human declared approval before the registration
  • The identity (DID) that made the declaration

WINDI DOES NOT PROVE:

  • That the content is true, accurate, or original
  • That the declarant is the author or owner
  • Legal validity, authentication, or public faith
  • That the content hasn't been copied or derived from elsewhere

Technical Details

Endpoint

https://windi-domain.com/mcp/

Transport

Streamable HTTP (JSON-RPC 2.0)

Authentication

OAuth 2.0 with PKCE (S256). Authorization via WINDI DID.

Metadata Endpoints

/.well-known/oauth-authorization-server
/.well-known/oauth-protected-resource

Supported Scopes

Privacy & Data Policy

WINDI never receives your documents. Only the SHA-256 hash (fingerprint) is transmitted. Your identity (DID) is used to attribute declarations. Session data is stored for authentication purposes only.

Read our full data policy →

Support

For questions or issues with the WINDI MCP Connector: