TrustNotch

com.trustnotchPublished by trustnotch.comv0.1.1Updated Oct 24, 2026

Tamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

TrustNotch gives an AI assistant tools to submit, fetch and verify tamper-evident audit logs with cryptographic proof bundles.

What you can do
Submit audit log entries for AI agent activity to TrustNotch and fetch them back later, with cryptographic proof bundles attached. Verify those proof bundles, optionally pinning a local public-key file for independent offline verification. Point the client at a chosen TrustNotch API base URL and use either a live or test API key.
When to use it
Use it when you need a verifiable, tamper-evident record of what an AI agent did, for example for audit trails, compliance evidence or post-hoc integrity checks. It is less useful if you only need ordinary application logging.
Requirements
Runs as a local process on the user's machine, launched with uvx from the trustnotch-mcp PyPI package, so a Python/uv runtime is needed. Requires a TrustNotch API key in TRUSTNOTCH_API_KEY (live or test). TRUSTNOTCH_API_URL sets the API base URL and TRUSTNOTCH_PUBKEYS_PATH optionally points to a local public-key file for offline verification. Desktop only; network access to the TrustNotch API.
Before you install
The API key in TRUSTNOTCH_API_KEY is a secret and grants access to your TrustNotch account; keep it out of shared configs. Submitting entries writes audit data to a third-party service, so consider what agent activity and metadata you send. Verification depends on the pinned public key, so a wrong or untrusted key file undermines the integrity check.

Installation

In SourceWeft

  1. Open TrustNotch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.