Attest by DataHubz (verify only)
com.datahubz/attest-verifyVersion 1.0.0Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in.
Status
Responds286 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:54 UTC
- Latency
- 286 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://attest.datahubz.com/mcp/verifyResponds286 msNo sign-in
Claude Code
claude mcp add --transport http attest-verify https://attest.datahubz.com/mcp/verifyClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: attest-verify
Remote MCP server URL: https://attest.datahubz.com/mcp/verifyCursor
{
"mcpServers": {
"attest-verify": {
"url": "https://attest.datahubz.com/mcp/verify"
}
}
}VS Code
code --add-mcp '{"name":"attest-verify","type":"http","url":"https://attest.datahubz.com/mcp/verify"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
1 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
verify_recordChecks 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Categories (suggested)
- Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared