# Attest by DataHubz (verify only) (remote · attest.datahubz.com)

Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `attest.datahubz.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify.md), [page](https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify)

## Channel facts

- Endpoint: `https://attest.datahubz.com/mcp/verify`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 556 tokens (~556/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Attest by DataHubz (verify only) MCP server?

Attest by DataHubz (verify only) is a hosted endpoint at https://attest.datahubz.com/mcp/verify, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-datahubz-attest-verify 'https://attest.datahubz.com/mcp/verify'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-datahubz-attest-verify": {
      "type": "http",
      "url": "https://attest.datahubz.com/mcp/verify"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-datahubz-attest-verify]
url = "https://attest.datahubz.com/mcp/verify"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-datahubz-attest-verify": {
      "type": "remote",
      "url": "https://attest.datahubz.com/mcp/verify",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-datahubz-attest-verify --url 'https://attest.datahubz.com/mcp/verify' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-datahubz-attest-verify:
    url: "https://attest.datahubz.com/mcp/verify"
```

### Netclaw

```json
{
  "McpServers": {
    "com-datahubz-attest-verify": {
      "Transport": "http",
      "Url": "https://attest.datahubz.com/mcp/verify"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-datahubz-attest-verify -t streamable-http -u 'https://attest.datahubz.com/mcp/verify'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 76, 0)

- [security] Tool “verify_record” rewrote its description, which is the text the model reads

### 2026-10-24 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `verify_record` (~335 tokens)

Verify an Attest 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.

Input parameters:

- `query` (string, required): An agreement ID, an ATT-XXXX-XXXX verification code, a receipt ID, a proof ID, or a SHA-256 fingerprint.

Output parameters:

- `agreement` (object)
- `found` (boolean)
- `link` (string): The page on attest.datahubz.com where anyone can see this check run again.
- `matches` (object)
- `proof` (object)
- `receipt` (object)
- `summary` (string): The result in one or two plain sentences, in Attest's words (no typed text), safe to repeat to the person.
- `type` (string): What was checked.
- `untrustedText` (object): Unverified text people typed into Attest (titles, notes, names, file names, claims, reasons), some of it by other parties; Attest didn't write it and doesn't check it.
- `verified` (boolean): True only when every check passed; summary says what that means for this record.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71

## Common questions

### What is the Attest by DataHubz (verify only) MCP server?

Attest by DataHubz (verify only) is an MCP server listed in the public MCP registry as com.datahubz/attest-verify. Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in. This page covers its hosted endpoint (https://attest.datahubz.com/mcp/verify).

### Is the Attest by DataHubz (verify only) MCP server safe to use?

Attest by DataHubz (verify only) scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Attest by DataHubz (verify only) MCP server expose?

Attest by DataHubz (verify only) exposes 1 tool: verify_record. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.

### Does the Attest by DataHubz (verify only) MCP server require authentication?

No. We connected to Attest by DataHubz (verify only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Attest by DataHubz (verify only) MCP server still maintained?

Attest by DataHubz (verify only) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Attest by DataHubz (verify only) MCP server?

VerifyMCP ran 13 checks on Attest by DataHubz (verify only), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://attest.datahubz.com/mcp/verify
- Repository: https://github.com/DataHubz/attest-mcp
- Website: https://attest.datahubz.com/docs/connector#verify-only
- Changelog RSS feed: https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify.json
- HTML version of this page: https://verifymcp.io/servers/com-datahubz-attest-verify/mcp-verify