STRIXTrust Center
Model Context Protocol

The Strix Verify Connector

Verify Strix governance decisions from inside your AI client. The connector is a read-only MCP server — no account, API key, or login. Add it to Claude, Claude Code, or ChatGPT, then ask for a record by its id: you get back the signed evidence and the exact command to re-verify it yourself, offline.

SetupToolsTrust model
MCP server · streamable HTTP

https://www.strixgov.com/api/mcp

Read-onlyNo authentication2 toolsEd25519 signed

The two tools

Both are read-only and require no authentication.

strix_verify

Verify a Strix governance evidence record by its evidenceId — the decision id, e.g. 5686. Returns the record’s verification status, the Ed25519 signing-key id, the signed canonical fields, and the one-line command to re-derive the verdict offline.

input: { evidenceId: string }

strix_governance_stats

Fetch public, aggregate governance statistics — decision counts, defined capabilities, bypass count, and engine state. Counts only; no tenant or personal data. A quick liveness snapshot.

input: none

Example

Asking your client to verify record 5686.

Prompt
Use strix_verify to check record 5686.
Response · abridged
{
  "verificationStatus": "VERIFIED_OFFLINE_BY_VERIFIER",
  "signingKeyId": "strix-prod-2026-05",
  "record": {
    "evidenceId": "5686",
    "capabilityId": "cron.evidenceOutboxRetry",
    "action": "allow",
    "actorRole": "automation",
    "createdAt": "2026-05-15T05:27:14.691Z",
    "evidenceHash": "1ac08c36…f961e2f0",
    "verifyWith": {
      "verifierCli": "npx @strixgov/verifier@latest 5686",
      "jwksUrl": "https://www.strixgov.com/.well-known/strix-jwks.json",
      "algorithm": "EdDSA",
      "curve": "Ed25519"
    }
  }
}

Reproduce the same verdict yourself, with no Strix code in the path:

npx @strixgov/verifier@latest 5686

Setup

The same endpoint everywhere: https://www.strixgov.com/api/mcp

Claude · web & desktop

  1. Open Settings → Connectors → Add custom connector.
  2. Name it Strix Verify and paste the MCP server URL above.
  3. Leave Authentication set to None and save. Claude runs the initialize handshake and lists the two tools.
  4. In a chat, enable the connector and ask: “Use strix_verify to check record 5686.”

Claude Code

Add the server from the CLI (streamable HTTP transport):

claude mcp add --transport http strix-verify https://www.strixgov.com/api/mcp

Confirm it registered:

claude mcp list

ChatGPT

  1. In Settings → Connectors, choose to add a custom / remote MCP connector. (Requires a plan tier that supports custom MCP connectors; you may need to enable developer mode.)
  2. Name it Strix Verify, paste the MCP server URL, and set Authentication to None.
  3. Save. ChatGPT runs initialize and tools/list; you’ll see strix_verify and strix_governance_stats.
  4. Enable it in a chat and ask: “Use strix_verify to check record 5686.”

Client menu labels change over time. The two constants are the URL (/api/mcp) and authentication (None). Look for “MCP”, “remote server”, or “custom connector”.

Trust model

What the connector can and can’t do.

Read-only

Both tools only read public governance data. The connector exposes no way to create, change, or delete anything.

No authentication

No account, API key, or login. The server is public; the same URL works for everyone.

Minimal input

The only input you provide is an evidence id for strix_verify. strix_governance_stats takes no input at all.

No tenant data

Stats are aggregate counts. A verified record returns signed canonical metadata — capability, action, actor role, timestamps, and hashes — not customer payloads.

Independently verifiable

Every signed record can be re-checked offline with npx @strixgov/verifier against the public JWKS (Ed25519). You don’t have to trust Strix’s tooling to trust the result.

Public key root

Signatures verify against keys published at the public JWKS endpoint — the same primitive an external auditor would use.

JWKS · https://www.strixgov.com/.well-known/strix-jwks.json
Verifier · npx @strixgov/verifier@latest <evidenceId>

A note on availability

A custom connector you add is scoped to your own workspace or account — adding it does not enable it for other Claude or ChatGPT users. The underlying verifier CLI (npx @strixgov/verifier) is public and works for anyone today.

References