ZKStamp Proof-100 vs io.github.many77146-bot/dmt-receipts
ZKStamp Proof-100 is an MCP server published by ZKStamp. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.many77146-bot/dmt-receipts is an MCP server published by many77146-bot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
| Marketplace |  ZKStamp Proof-100 |  io.github.many77146-bot/dmt-receipts |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.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
| Fact | ZKStamp Proof-100 | io.github.many77146-bot/dmt-receipts |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-27 | Not published |
| Where it runs (differs) | Remote server (proof.zketernity.app/mcp) | On your machine (https://github.com/many77146-bot/dmt-receipts/releases/download/v0.1.0/dmt-receipts-0.1.0.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/zkstamp/proof100 | github.com/many77146-bot/dmt-receipts |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-27 | 2026-11-05 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | no remote endpoint we check |
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
ZKStamp Proof-100
Shielded proof-of-existence timestamps on BitcoinZ (zk-SNARKs). Free trial: 3 proofs.
io.github.many77146-bot/dmt-receipts
Stamp and verify Bitcoin-anchored OpenTimestamps memory receipts for AI agents.
How to run each
ZKStamp Proof-100 As a remote MCP server
claude mcp add --transport http proof100 https://proof.zketernity.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
io.github.many77146-bot/dmt-receipts
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ZKStamp Proof-100 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: ZKStamp Proof-100 · What it can do: io.github.many77146-bot/dmt-receipts · Compare two other plugins
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.