Ext Ops Panel
Open dashboard
Comparison

weilliptic-receipts vs Attest by DataHubz (verify only)

weilliptic-receipts is a plugin bundle for AI coding tools published by weilliptic-public. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Attest by DataHubz (verify only) is an MCP server published by datahubz.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceweilliptic-receiptsAttest by DataHubz (verify only)
Claude Code: claude-plugins-community Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

weilliptic-receipts vs Attest by DataHubz (verify only)
Factweilliptic-receiptsAttest by DataHubz (verify only)
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (attest.datahubz.com/mcp/verify)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)6Not published
Parts of the bundle (differs)7Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/weilliptic-public/claude-code-hooksgithub.com/datahubz/attest-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-14
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

weilliptic-receipts

In its own words, on Claude Code: claude-plugins-community:

Claude Code plugin that audits AI-assisted code changes. Automatically records every file edit, session, and commit as a verifiable receipt providing tamper-proof provenance for AI-generated code.

Attest by DataHubz (verify only)

In its own words, on Official MCP Registry:

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

How to run each

weilliptic-receipts As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install weilliptic-receipts@claude-community

Attest by DataHubz (verify only) As a remote MCP server

Claude Code
claude mcp add --transport http attest-verify https://attest.datahubz.com/mcp/verify

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Attest by DataHubz (verify only) has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: weilliptic-receipts · What it can do: Attest by DataHubz (verify only) · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built