io.github.bytewizard42i/soulsketch
NPM · @SOULSKETCH/MCP-SERVER · SCANNED SEP 20
Portable, user-owned AI memory packs: read, validate, fingerprint, diff, and observe
Available components
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 Security98
- 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
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 52 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 669 tokens (~111/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the io.github.bytewizard42i/soulsketch MCP server?
io.github.bytewizard42i/soulsketch runs locally as an npm package, launched with npx -y @soulsketch/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @soulsketch/mcp-server
claude mcp add bytewizard42i-soulsketch -- npx -y @soulsketch/mcp-server
{
"mcpServers": {
"bytewizard42i-soulsketch": {
"command": "npx",
"args": [
"-y",
"@soulsketch/mcp-server"
]
}
}
} {
"servers": {
"bytewizard42i-soulsketch": {
"command": "npx",
"args": [
"-y",
"@soulsketch/mcp-server"
]
}
}
} codex mcp add bytewizard42i-soulsketch -- npx -y @soulsketch/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bytewizard42i-soulsketch": {
"type": "local",
"command": [
"npx",
"-y",
"@soulsketch/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add bytewizard42i-soulsketch --command npx --arg -y --arg @soulsketch/mcp-server
mcp_servers:
bytewizard42i-soulsketch:
command: "npx"
args: ["-y", "@soulsketch/mcp-server"] {
"McpServers": {
"bytewizard42i-soulsketch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@soulsketch/mcp-server"
]
}
}
} assistant mcp add bytewizard42i-soulsketch -t stdio -c npx -a -y @soulsketch/mcp-server
{
"mcpServers": {
"bytewizard42i-soulsketch": {
"command": "npx",
"args": [
"-y",
"@soulsketch/mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −3
- Stability: pass → 0.80 functional
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/@soulsketch/mcp-server@1.3.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| 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 →
soulsketch_continuity_record Create a continuity record ~136
Build a full continuity record for a pack: fingerprint, per-file hashes, provenance labels (source, authority, trust), and provenance warnings. This is the audit artifact to store alongside the pack or anchor elsewhere.
| Name | Type | Req | Description |
|---|---|---|---|
| authority | string | – | How authoritative this pack state is |
| commit | string | – | Git commit hash pinning this state |
| pack_dir | string | yes | Absolute path to the memory pack directory |
| repo | string | – | Repository that owns this state |
| source | string | – | How the memory content was produced |
| trust_label | string | – | Sensitivity classification of the contents |
No output schema declared.
No examples provided.
soulsketch_diff_packs Diff two memory packs ~82
Compare two memory pack directories and explain WHICH identity dimension changed (persona, relationships, technical domains, voice, observations). Line-ending differences (CRLF vs LF) never count as identity changes.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_dir_a | string | yes | Absolute path to the first pack directory |
| pack_dir_b | string | yes | Absolute path to the second pack directory |
No output schema declared.
No examples provided.
soulsketch_fingerprint_pack Fingerprint a memory pack ~70
Compute the deterministic SHA-256 identity fingerprint of a memory pack, plus per-file hashes. The fingerprint refers to a memory state without revealing its contents; use it for audit logs, handoffs, and continuity proofs.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_dir | string | yes | Absolute path to the memory pack directory |
No output schema declared.
No examples provided.
soulsketch_observe Append a runtime observation ~167
Append ONE observation line to the pack's runtime_observations.jsonl (the living memory stream). This is the only write this server can perform: append-only, never modifying or deleting existing memories. MEMORY ETIQUETTE: when the conversation surfaces something memory-worthy (a durable preference, a decision, a milestone, a relationship change), FIRST ask the user, e.g. "Would you like me to save this to your Soul-Sanctum?" - and only call this tool after they agree. Never save silently; the user owns their memory.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Who is recording this (e.g. assistant name) |
| note | string | yes | The observation to remember |
| pack_dir | string | yes | Absolute path to the memory pack directory |
No output schema declared.
No examples provided.
soulsketch_read_pack Read a memory pack ~144
Load the contents of a memory pack so the assistant can adopt its identity: persona, relationships, technical context, voice, and recent observations. Optionally restrict to specific files. ONE SOUL, MANY VESSELS: the pack is a single shared identity. If persona.md has a "Vessels" section listing a name for the tool you are running in, adopt that name (and use it as the author when observing) while keeping the shared persona, relationships, and voice.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Optional subset of pack files to read (default: all five) |
| pack_dir | string | yes | Absolute path to the memory pack directory |
No output schema declared.
No examples provided.
soulsketch_validate_pack Validate a memory pack ~70
Check that a directory is a healthy 5-file SoulSketch memory pack (persona.md, relationship_dynamics.md, technical_domains.md, stylistic_voice.md, runtime_observations.jsonl). Returns errors and warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_dir | string | yes | Absolute path to the memory pack directory |
No output schema declared.
No examples provided.
What is the io.github.bytewizard42i/soulsketch MCP server?
io.github.bytewizard42i/soulsketch is an MCP server listed in the public MCP registry as io.github.bytewizard42i/soulsketch. Portable, user-owned AI memory packs: read, validate, fingerprint, diff, and observe. This page covers its npm package (@soulsketch/mcp-server).
Is the io.github.bytewizard42i/soulsketch MCP server safe to use?
io.github.bytewizard42i/soulsketch scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.bytewizard42i/soulsketch MCP server expose?
io.github.bytewizard42i/soulsketch exposes 6 tools: soulsketch_validate_pack, soulsketch_fingerprint_pack, soulsketch_diff_packs, soulsketch_read_pack, soulsketch_observe, soulsketch_continuity_record. Their descriptions and schemas cost roughly 669 tokens of context every time the server is loaded.
Is the io.github.bytewizard42i/soulsketch MCP server still maintained?
io.github.bytewizard42i/soulsketch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bytewizard42i/soulsketch MCP server under?
io.github.bytewizard42i/soulsketch declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.