Attest by DataHubz (verify only) MCP server
com.datahubz/attest-verifydatahubz.comstreamable-httpv1.0.0Scanned
Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in.
1 tool: 1 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Attest by DataHubz (verify only) MCP server can do
The Attest by DataHubz (verify only) MCP server is published by datahubz.com, a domain the MCP Registry verified. It has 1 tool. It can create or change data (1 tool: verify_record), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Changes things 1Claude Code: ask
verify_recordChecks whether a signed document, an agreement, a receipt or a Share proof is genuine, and what it says.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify an Attest record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://attest.datahubz.com/.well-known/oauth-protected-resource
- Authorization servers
- https://attest.datahubz.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://attest.datahubz.com/mcp/verify: tools/list returned 1 tool to an anonymous client, including verify_record (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:verify_recordChanges thingsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http attest-verify https://attest.datahubz.com/mcp/verifyclaude mcp add --transport http attest-verify https://attest.datahubz.com/mcp/verifyRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__attest-verify__verify_record"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as attest-verify. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.datahubz/attest-verify/verify?hash=12c84c31f17f0f0581a9f565eed7234d89dd45f477a92c130756f1510a370eb0" | jq -e '.changed == false'Pinned hash 12c84c31f17f, from Nov 10, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.datahubz/attest-verify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.datahubz/attest-verify)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:53 UTC.
Attest by DataHubz (verify only) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Attest by DataHubz (verify only) MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Attest by DataHubz (verify only) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Attest by DataHubz (verify only) MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Attest by DataHubz (verify only) MCP server have?
- 1 tool: 1 write. verify_record.
Does the Attest by DataHubz (verify only) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Attest by DataHubz (verify only) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Attest by DataHubz (verify only) MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.