# io.github.many77146-bot/dmt-receipts (mcpb · dmt-receipts-0.1.0.mcpb)

Stamp and verify Bitcoin-anchored OpenTimestamps memory receipts for AI agents.

- Trust score: 44/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- mcpb · `dmt-receipts-0.1.0.mcpb`: 44/100 (this document), [markdown](https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts.md), [page](https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/many77146-bot/dmt-receipts/releases/download/v0.1.0/dmt-receipts-0.1.0.mcpb`
- Transport: `stdio`
- SHA-256: `58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-06.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 23/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 259 tokens (~129/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 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 io.github.many77146-bot/dmt-receipts MCP server?

io.github.many77146-bot/dmt-receipts ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/many77146-bot/dmt-receipts/releases/download/v0.1.0/dmt-receipts-0.1.0.mcpb`
- SHA-256: `58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7`

### Verify on macOS / Linux

```bash
echo "58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7  dmt-receipts-0.1.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\dmt-receipts-0.1.0.mcpb).Hash -eq "58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7"
```

## 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-06 (score 44, +1)

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

### 2026-11-05 (score 43)

First indexed and scored.

## MCP tools (2)

### `stamp_memory` (~147 tokens)

Canonicalize a dmt-memory/v1 JSON memory, SHA-256 it, stamp the digest on public OpenTimestamps calendars, and return the memory plus a base64 .ots receipt. Proves the exact bytes existed no later than a Bitcoin block time; does not prove authorship. Stores nothing.

Input parameters:

- `agent_id` (string, required): Stable agent identifier
- `content` (required): Memory payload (string, object, array, number, or boolean)
- `created_at` (string): Optional ISO-8601 UTC timestamp ending in Z; defaults to now
- `key` (string, required): Memory key / slug / path
- `tags` (array): Optional string tags; defaults to []

### `verify_receipt` (~112 tokens)

Locally check that a base64 OpenTimestamps receipt header and digest match a dmt-memory/v1 object's canonical SHA-256. Does not validate calendar operations or Bitcoin inclusion; use ots upgrade/verify for full proof verification.

Input parameters:

- `memory` (object, required): Full dmt-memory/v1 object (agent_id, key, content, tags, created_at)
- `ots_base64` (string, required): Base64-encoded .ots receipt
- `sha256` (string): Optional expected hex digest to cross-check

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts#diagnostics

## Score history

- 2026-11-06: 44
- 2026-11-05: 43

## Common questions

### What is the io.github.many77146-bot/dmt-receipts MCP server?

io.github.many77146-bot/dmt-receipts is an MCP server listed in the public MCP registry as io.github.many77146-bot/dmt-receipts. Stamp and verify Bitcoin-anchored OpenTimestamps memory receipts for AI agents. This page covers its MCPB bundle (https://github.com/many77146-bot/dmt-receipts/releases/download/v0.1.0/dmt-receipts-0.1.0.mcpb).

### Is the io.github.many77146-bot/dmt-receipts MCP server safe to use?

io.github.many77146-bot/dmt-receipts scores 44 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 io.github.many77146-bot/dmt-receipts MCP server expose?

io.github.many77146-bot/dmt-receipts exposes 2 tools: stamp_memory, verify_receipt. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.

### What licence is the io.github.many77146-bot/dmt-receipts MCP server under?

io.github.many77146-bot/dmt-receipts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.many77146-bot/dmt-receipts MCP server?

VerifyMCP ran 15 checks on io.github.many77146-bot/dmt-receipts, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.many77146-bot/dmt-receipts: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Changelog RSS feed: https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts.xml
- Changelog JSON feed: https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts.json
- HTML version of this page: https://verifymcp.io/servers/many77146-bot-dmt-receipts/dmt-receipts
