Attest by DataHubz (verify only)
v1.0.0Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in.
Endpoint health
online- Last checked
- 11/3/2026, 8:17:13 PM
- Latency
- 83 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.datahubz%2Fattest-verify
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.datahubz/attest-verify": {
"url": "https://attest.datahubz.com/mcp/verify"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
1 shown · authentication unknown
Verify an Attest record
verify_record
Checks whether a signed document, an agreement, a receipt or a Share proof is genuine, and what it says. It runs the same public check anyone can run at attest.datahubz.com/verify, with no account. It takes one of: an agreement ID (agr_...), the verification code printed on the signed copy, at the foot of every page and on its signature stamps (ATT-XXXX-XXXX), a receipt ID (rcpt_...), a Share proof ID (azk_...), or a SHA-256 fingerprint (64 hex characters) of a file. For a signed agreement it returns its status, each signer's name and signing time, whether every passkey signature checks out, and its blockchain anchor (on Horizen or Base, as the record names). A private agreement is reported as private: its parties verify it through zero-knowledge proofs instead. It takes a file's fingerprint, never the file itself: the SHA-256 can be computed on the person's device (for example shasum -a 256 file.pdf), or the file dropped on attest.datahubz.com/verify, where it is fingerprinted in the browser and never uploaded. Text people typed (titles, notes, names, claims) comes only in untrustedText fields, apart from Attest's own wording. Email addresses, wherever they appear, were typed by people too (a sender chooses the signers' addresses) and are unverified input.
Schema valid · SHA-256 a9dafce6f6f6…
View input schema
{ "type": "object", "properties": { "query": { "type": "string", "minLength": 1, "maxLength": 200, "description": "An agreement ID, an ATT-XXXX-XXXX verification code, a receipt ID, a proof ID, or a SHA-256 fingerprint." } }, "required": [ "query" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://attest.datahubz.com/mcp/verify