Armadoc
NPM · ARMADOC
Send and read end-to-end encrypted documents. Your private key never leaves your machine.
Available components
Last scanned (10 hours ago)
Scores higher than 72% of npm servers
Category Documents and Files
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to waimun/armadoc-cli). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 284 tokens (~94/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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
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.
- 22 Oct 26 +5
- Stability: unverified → 0.30 ▲ functional
- 13 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.2.0 → 0.2.1 functional
- 9 Oct 26 32
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 23 Oct 2026 · Analysed npm/armadoc@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | waimun/armadoc-cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/waimun/armadoc-cli/.github/workflows/publish.yml@refs/tags/v0.2.1 |
| Rekor log index | 3188044429 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:275cd213d8a4b7b4ca7f994255fef51743be2363073745c58da1ffb9949921a7b67d335d4db7c4e44f2276b2eafc46971521b8a71acc25719dd1d75f0 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
list_documents List documents ~56
Lists the Armadoc documents and invites still open on your account: inbound (sent to you) and outbound (sent by you). Times are ISO 8601.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Only this direction; both when omitted |
No output schema declared.
No examples provided.
read_document Read a document ~100
Decrypts a document sent to you and saves its files to disk. Returns the paths, names and sizes of the saved files, not their contents; read them from disk if needed. Never overwrites an existing file.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Absolute directory to save into; defaults to a per-link Armadoc download folder |
| linkId | string | yes | The link id, the last segment of an armadoc.link/v/ URL |
No output schema declared.
No examples provided.
send_document Send a document ~128
Encrypts local files on this machine and sends them to one recipient, as you. The recipient gets an email with a link. A recipient with no Armadoc key is emailed an invite instead and nothing is uploaded; once they accept, call this again with the same files to complete it.
| Name | Type | Req | Description |
|---|---|---|---|
| expirySecs | integer | – | How long the link stays open, in seconds; default 864000 |
| paths | array | yes | Absolute paths of the files to send |
| recipientEmail | string | yes | The recipient's email address |
| recipientName | string | yes | The recipient's name |
No output schema declared.
No examples provided.
How do I install the Armadoc MCP server?
Armadoc runs locally as an npm package, launched with npx -y armadoc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · armadoc
claude mcp add link-armadoc-armadoc -- npx -y armadoc
What is the Armadoc MCP server?
Armadoc is an MCP server listed in the public MCP registry as link.armadoc/armadoc. Send and read end-to-end encrypted documents. Your private key never leaves your machine. This page covers its npm package (armadoc).
Is the Armadoc MCP server safe to use?
Armadoc scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Armadoc MCP server expose?
Armadoc exposes 3 tools: list_documents, read_document, send_document. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.
Is the Armadoc MCP server still maintained?
Armadoc is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.