Who it is for
Professionals who must evidence that human review preceded a filing or approval.
eIDAS-qualified timestamps proving a human reviewed a document
Overview
ZTR records that a person reviewed a document, which is a different problem from checking the document itself. When a professional signs off before filing or approving, ZTR hashes the file with SHA-256, timestamps the declaration through an eIDAS-qualified timestamping authority operated by Aruba PEC S.p.A., and returns a receipt sealed with an HMAC.
The document is discarded immediately and never stored or transmitted beyond its hash, so the record shows review occurred without holding the content. Receipts download as PDF reports carrying QR codes for independent third-party checking. The publisher describes it as a free technical preview. Community tier.
Professionals who must evidence that human review preceded a filing or approval.
Four tools answered against three claimed: verify_document creates the record, while check_receipt, list_receipts and download_receipt_pdf retrieve it afterwards.
Availability
ZTR — Temporal Registry is listed in the Claude connectors directory only. Temporal Registry has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
ZTR — Temporal Registry publishes 3 tools to Claude, a deliberately narrow surface; only 11.3% of the 1,253 Claude-listed connectors expose fewer.
The median Claude-listed connector filed under Legal publishes 11, so this one sits 8 tools below its bucket's median, 27th of 33.
It falls in the 1-3 tools band, which holds 16.4% of the Claude directory.
A direct call to the endpoint returned 4 tools, 1 more than the 3 the listing publishes. Probed 2026-08-07.
verify_documentcheck_receiptlist_receiptsdownload_receipt_pdfZTR — Temporal Registry publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
https://temporalregistry.com/mcp ZTR — Temporal Registry is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality.
In the publisher's words
ZTR creates contemporaneous records of human verification for AI-assisted documents. When a professional reviews a document before filing, submitting, or approving it, ZTR hashes the document (SHA-256), timestamps the professional's declaration via an eIDAS-qualified TSA (Aruba PEC S.p.A.), and returns a retrievable receipt with HMAC integrity seal. The document is immediately discarded — never stored or transmitted beyond the hash. Receipts can be downloaded as professional PDF reports with QR codes for independent third-party verification. Currently in free technical preview.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Nearby
Primary US legal authority with deterministic citation review
Claude
In-house legal workspace: knowledge base answers and review playbooks
Claude
A lawyer network's discussions, opportunities, templates and benchmarks
Claude
EU cybersecurity and privacy compliance work with cited sources
Claude
German tax law as a knowledge graph resolved by assessment period
Claude
Chilean case law, legislation, doctrine and CGR rulings with citations
Claude
This is an independent catalogue entry compiled by Node8 from ZTR — Temporal Registry's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Temporal Registry, and inclusion here is not an endorsement.
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.