io.github.many77146-bot/dmt-receipts
MCPB · DMT-RECEIPTS-0.1.0.MCPB
Stamp and verify Bitcoin-anchored OpenTimestamps memory receipts for AI agents.
Available components
Last scanned (6 hours ago)
Scores higher than 74% of MCPB servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security23
- 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.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 259 tokens (~129/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityNo 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.
- Stability in Stability & Change Management (scores 0 for this)Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed mcpb/https://github.com/many77146-bot/dmt-receipts/releases/download/v0.1.0/dmt-receipts-0.1.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
stamp_memory ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Stable agent identifier |
| content | – | yes | Memory payload (string, object, array, number, or boolean) |
| created_at | string | – | Optional ISO-8601 UTC timestamp ending in Z; defaults to now |
| key | string | yes | Memory key / slug / path |
| tags | array | – | Optional string tags; defaults to [] |
No output schema declared.
No examples provided.
verify_receipt ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memory | object | yes | Full dmt-memory/v1 object (agent_id, key, content, tags, created_at) |
| ots_base64 | string | yes | Base64-encoded .ots receipt |
| sha256 | string | – | Optional expected hex digest to cross-check |
No output schema declared.
No examples provided.
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.
mcpb · dmt-receipts-0.1.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7
macOS / Linux
echo "58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7 dmt-receipts-0.1.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\dmt-receipts-0.1.0.mcpb).Hash -eq "58a57206daac47b2bfb905c835c1987d3a35f87ebbe18de3fff9d598ebd2f4c7"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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 43 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 14 checks on io.github.many77146-bot/dmt-receipts, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.many77146-bot/dmt-receipts: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.