io.github.Spacetime-Technology/safehold

NPM · SAFEHOLD · SCANNED AUG 3

Local, encrypted MCP vault for passports, IDs, visas and photos. You control access.

Available components

+25 this week 78 78 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency97

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Cryptographically verified build provenance (signed, bound to Spacetime-Technology/safehold). View diagnostics → Pass
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 76 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability85

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 855 tokens (~77/item across 11 items; 11 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).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

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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · safehold

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add spacetime-technology-safehold -- npx -y safehold

# add to Codex CLI

codex mcp add spacetime-technology-safehold -- npx -y safehold

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "spacetime-technology-safehold": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "safehold"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add spacetime-technology-safehold --command npx --arg -y --arg safehold

# ~/.hermes/config.yaml

mcp_servers:
  spacetime-technology-safehold:
    command: "npx"
    args: ["-y", "safehold"]

// mcp.json

{
  "mcpServers": {
    "spacetime-technology-safehold": {
      "command": "npx",
      "args": [
        "-y",
        "safehold"
      ]
    }
  }
}

Changelog

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.

2 Aug 26 +52
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: Spacetime-Technology/safehold security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 +21
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
31 Jul 26 −48
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 53

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:: Spacetime-Technology/safehold
Certificate issuer:: https://token.actions.githubusercontent.com
Certificate SAN:: https://github.com/Spacetime-Technology/safehold/.github/workflows/release.yml@refs/tags/v1.2.0
Rekor log index:: 1566625899
Predicate type:: https://slsa.dev/provenance/v1
Subject digest:: sha512:1e6bf24559f06eaab8450766e37d4d2b2829271517e39ba8d6a1637c937d266991f5d8eaf6eecb9d6a64b7b98dc6157cf97bf29e96b0f9d8d3d5c5722
Discovery method:: attestation_endpoint

Dependencies 96 packages

96 packages in the resolved dependency tree · 96 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 11 exposed · ~825 tokens

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.

Tool Tokens

add_document ~103

Add a new document to the vault. The document is stored locally and encrypted. Known document types (passport, national_id, driving_license, visa, photo_*) are strictly validated.

Input Output Examples

Name	Type	Req	Description
document_type	string	yes	The type of document (e.g. "passport", "visa")
fields	object	yes	The document field values to store
label	string	yes	A human-readable label for this document, e.g. "UK Passport 2024"

No output schema declared.

No examples provided.

delete_document ~31

Permanently delete a document from the vault.

Input Output Examples

Name	Type	Req	Description
id	string	yes	The ID of the document to delete

No output schema declared.

No examples provided.

get_access_log ~61

View the history of document field accesses — what was shared, with which client, and when.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Filter entries to a specific document ID
limit	integer	—	Maximum number of log entries to return (default 50)

No output schema declared.

No examples provided.

get_document ~112

Retrieve fields from any document type not covered by a dedicated tool. The user will be prompted for consent before any data is returned.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Specific document id (required when more than one of this type is stored)
document_type	string	yes	The document type to retrieve (e.g. "insurance_card")
fields	array	yes	The field names to retrieve from the document
purpose	string	yes	Why the calling agent needs this data — shown to the user for consent

No output schema declared.

No examples provided.

get_driving_license ~86

Retrieve specific fields from a stored driving licence. The user will be prompted for consent before any data is returned.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Specific driving licence id (required when more than one is stored)
fields	array	yes	The driving licence fields to retrieve
purpose	string	yes	Why the calling agent needs this data — shown to the user for consent

No output schema declared.

No examples provided.

get_national_id ~87

Retrieve specific fields from a stored national identity card. The user will be prompted for consent before any data is returned.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Specific national ID id (required when more than one is stored)
fields	array	yes	The national ID fields to retrieve
purpose	string	yes	Why the calling agent needs this data — shown to the user for consent

No output schema declared.

No examples provided.

get_passport ~83

Retrieve specific fields from a stored passport. The user will be prompted for consent before any data is returned.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Specific passport id (required when more than one passport is stored)
fields	array	yes	The passport fields to retrieve
purpose	string	yes	Why the calling agent needs this data — shown to the user for consent

No output schema declared.

No examples provided.

get_photo ~90

Retrieve a stored photo. Returns base64-encoded image data. The user will be prompted for consent before any data is returned.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Specific photo id (required when more than one of this type is stored)
purpose	string	yes	Why the calling agent needs this photo — shown to the user for consent
type	string	yes	The type of photo to retrieve

No output schema declared.

No examples provided.

get_visa ~83

Retrieve specific fields from a stored visa. The user will be prompted for consent before any data is returned.

Input Output Examples

Name	Type	Req	Description
document_id	string	—	Specific visa id (required when more than one visa is stored)
fields	array	yes	The visa fields to retrieve
purpose	string	yes	Why the calling agent needs this data — shown to the user for consent

No output schema declared.

No examples provided.

list_documents ~29

List all stored documents. Returns metadata only (type, label, expiry) — no sensitive field values.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_document ~60

Update fields on an existing document. Only the provided keys are changed. Known document types are strictly validated.

Input Output Examples

Name	Type	Req	Description
fields	object	yes	The fields to update — only provided keys are changed
id	string	yes	The ID of the document to update

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug