Attest by DataHubz

com.datahubzPublished by datahubz.comOfficial publisherv1.0.0Updated Oct 24, 2026

Track agreements sent for signature, remind signers, verify signed documents and share proofs.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Attest by DataHubz is a hosted MCP server that lets an assistant track e-signature agreements, remind signers, verify signed records and create proofs.

What you can do
List and read agreements you sent or must sign, with status, signers, whose turn it is and the audit trail, plus account usage and signing-key status. Remind signers whose turn it is by emailing the signing link again, at most once a day each. Prepare a new agreement by filling in Attest's New agreement form and returning a link; you attach the PDF and send it in Attest. Verify a signed document, receipt or proof by stamp code, ID or SHA-256 fingerprint, including the Horizen blockchain anchor. Record and list public receipts for SHA-256 fingerprints, and create Share proofs, submitted to zkVerify, that you signed a completed agreement.
When to use it
Useful when you handle agreements in Attest and want an assistant to answer questions about what is pending, nudge signers, draft a new agreement's details, or check that a signed document or receipt is genuine. The public verify endpoint works without an account for checking records you received.
Requirements
A remote Streamable HTTP endpoint at attest.datahubz.com/mcp; nothing runs locally. OAuth sign-in to an Attest account is required, with a consent page granting permissions. A separate verify-only endpoint needs no sign-in. Network access is required.
Before you install
Acting on your records is irreversible: reminders are emailed to signers, and receipts and public Share proof links cannot be undone or withdrawn. Share proofs reveal your email address, any named co-signer's, and the completion date. Receipts store a public fingerprint. Documents stay encrypted and the connector cannot read or sign them; compute a file's SHA-256 on your device rather than uploading it. Review the consent page and granted permissions, and disconnect unused apps.

Installation

In SourceWeft

  1. Open Attest by DataHubz in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.datahubz%2Fattest/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "attest-by-datahubz": {
      "type": "http",
      "url": "https://attest.datahubz.com/mcp"
    }
  }
}

README

Attest by DataHubz: the Attest connector

Attest by DataHubz is document signing and verifiable records. The Attest connector lets your assistant list the agreements you sent or must sign, remind signers, prepare new agreements, verify signed documents and records anchored on the Horizen blockchain, and create Share proofs, zero-knowledge proofs verified on zkVerify. It never reads a document and never signs: documents stay end-to-end encrypted, and each signer signs in Attest with their own passkey.

This repository holds the configuration that installs the connector in Gemini CLI and Cursor. The connector itself is a hosted MCP server at https://attest.datahubz.com/mcp; nothing here runs on your machine.

Documentation: https://attest.datahubz.com/docs/connector

What you can do

  • See your agreements: the ones you sent and the ones waiting for your signature, with their status, signers, whose turn it is and the audit trail up to completion.
  • Remind signers of an agreement you sent: the signing link goes again to the signers whose turn it is, at most once a day each.
  • Prepare a new agreement: give the title, signers, signing order, a note and an expiry date, and get a link to Attest's New agreement form, filled in. You attach the PDF and send it in Attest, where it is encrypted in your browser.
  • Verify a signed document: give the code on its signature stamp (ATT-XXXX-XXXX), an agreement, receipt or proof ID, or the file's SHA-256 fingerprint. Attest reports who signed, whether every passkey signature checks out, and the record's anchor on the Horizen blockchain. Anyone can run this check, without an account.
  • Prove you signed an agreement without revealing it: a Share proof shows your email address (and a co-signer's, if you name one) and the day the agreement was completed, never the document, its terms or its title. Each proof is submitted to zkVerify for independent verification.
  • Record a receipt: anchor a SHA-256 fingerprint on Horizen as proof that the content existed, unchanged, at that time, and list your receipts.

Try: "Which agreements are waiting for my signature?", "Who still needs to sign the agreements I sent?", "Prepare a mutual NDA for Mary Ruiz to sign."

Install

Gemini CLI

bash
gemini extensions install https://github.com/DataHubz/attest-mcp

Or add only the server: gemini mcp add --transport http attest https://attest.datahubz.com/mcp. Gemini CLI finds Attest's sign-in on its own; run /mcp auth attest to sign in, and again if it asks you to later.

Cursor and VS Code

The connector's documentation has one-click install links for both: https://attest.datahubz.com/docs/connector#add. Or add it to Cursor's ~/.cursor/mcp.json (or .cursor/mcp.json in a project), or install the Attest plugin from the Cursor Marketplace once it is listed there:

json
{  "mcpServers": {    "attest": { "url": "https://attest.datahubz.com/mcp" }  }}

Cursor finds Attest's sign-in on its own and asks you to sign in the first time it connects. In VS Code, run MCP: Add Server from the Command Palette with the same URL; the entry in .mcp.json is {"mcpServers": {"attest": {"type": "http", "url": "https://attest.datahubz.com/mcp"}}}.

Claude, Claude Code, ChatGPT, Copilot Studio and other MCP apps

  • Claude: Customize, then Connectors, + Add, then Add custom connector. Name it Attest, enter https://attest.datahubz.com/mcp, choose Sign in now, then Use Claude's published identity (Register automatically works too), add it and choose Connect.
  • Claude Code: claude mcp add --transport http attest https://attest.datahubz.com/mcp, then /mcp to sign in.
  • ChatGPT: open chatgpt.com/plugins, choose +, then Add custom MCP server. Name it Attest, enter the same URL, choose OAuth, confirm the warning and choose Create as a plugin.
  • Microsoft Copilot Studio: on the agent's Tools page, Add a tool, New tool, Model Context Protocol; the same URL, with OAuth 2.0 and Dynamic discovery.
  • Any app that connects to an MCP server by URL over Streamable HTTP can use https://attest.datahubz.com/mcp.

Verify without an account

https://attest.datahubz.com/mcp/verify offers verify_record only, with no sign-in. Use it to check a signed document, a receipt or a proof you received.

Sign-in and permissions

When an app connects, it sends you to Attest. You sign in, and a consent page shows who is asking, the address it returns to, and what it will be able to do. An app that identifies itself with a registration it publishes, as ChatGPT and Claude can, is shown with the site that publishes it (for example, identified by chatgpt.com); an app that registered itself is shown by the name it gives itself, marked as not verified by Attest. You can untick a permission, and the app gets nothing until you choose Allow.

PermissionWhat it allows
Check recordsPublic checks of agreements, receipts, proofs and fingerprints
Read your recordsYour agreements, receipts, Share proofs and plan usage
Act on your recordsEmail your signers reminders, record public receipts and create public Share proof links (none of these can be undone or withdrawn), and prepare agreements for you to finish in Attest

The Security page in Attest lists each connected app with its permissions and last use; Disconnect ends its access at once.

What it can't do, by design

  • It can't read your documents. Every document is end-to-end encrypted in the sender's browser, and Attest stores it only as ciphertext it can't read, so no tool reads, summarizes or returns a document.
  • It can't sign. Each signer signs in Attest with their own passkey (Face ID, Touch ID, Windows Hello or the device PIN).
  • It doesn't send documents. You send them from Attest.
  • It never takes a file. To check a file, your assistant computes its SHA-256 on your device (shasum -a 256 file.pdf) or you drop it on https://attest.datahubz.com/verify, where it is fingerprinted in your browser and never uploaded.

Tools

ToolWhat it does
verify_recordChecks an agreement ID, the ATT-XXXX-XXXX code on a signature stamp, a receipt ID, a proof ID or a SHA-256 fingerprint: the same public check anyone can run on the verify page
list_agreementsYour agreements, sent and received: status, signers, dates, whose turn it is, whether it's anchored, and the certificate link, in pages
get_agreementOne agreement, with the note to signers, the document's fingerprint and the audit trail up to completion
remind_signersEmails the signing link again to the signers whose turn it is, at most once a day per signer
prepare_agreementFills in the New agreement form and gives you the link; you attach the PDF and send it
record_receiptRecords a receipt for a SHA-256 fingerprint, or for a short text it fingerprints; only the fingerprint is stored, and it is public
list_receiptsYour receipts, with their fingerprints, claims and anchors, in pages
share_proofCreates a Share proof that you signed a completed agreement, alone or with a named co-signer, and gives you its link
get_accountWhat your account has left to use, and whether your signing key is set up

Privacy, terms and support

License

MIT, for the files in this repository (the same license as DataHubz's open-source verifier, https://github.com/DataHubz/attest-verifier). Attest itself is a hosted service at attest.datahubz.com.

Source: README.md at commit a33e9cf

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Datahubz integrations

Attest by DataHubz (verify only)

com.datahubzOfficial publisher

Remote MCP server for Attest by DataHubz that lets an assistant check agreement status, prepare new agreements, and publicly verify signed documents, receipts,

Streamable HTTPWeb executable
Productivity & Workflow1 toolOct 25, 2026