io.github.sparkvibe-io/memorymesh
PYPI · MEMORYMESH
Persistent, zero-dependency AI memory using SQLite. Local-first, cross-tool portable.
Available components
Last scanned (21 hours ago)
Scores higher than 17% of PyPI servers
Category Memory and Knowledge
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency73
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to sparkvibe-io/memorymesh). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 245 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- License: fail → pass ▲ functional
- Licence: MIT License → MIT functional
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 4 Nov 2026 · Analysed pypi/memorymesh@4.1.0
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sparkvibe-io/memorymesh |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sparkvibe-io/memorymesh/.github/workflows/publish.yml@refs/tags/v4.1.0 |
| Rekor log index | 1004648280 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:2043009f3d3caedbef4a3dc6e47517cb7b9eb0ee0c7ec3f04a77efe295c5eeee |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.sparkvibe-io/memorymesh MCP server?
io.github.sparkvibe-io/memorymesh runs locally as a PyPI package, launched with uvx memorymesh. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · memorymesh
claude mcp add sparkvibe-io-memorymesh -- uvx memorymesh
What is the io.github.sparkvibe-io/memorymesh MCP server?
io.github.sparkvibe-io/memorymesh is an MCP server listed in the public MCP registry as io.github.sparkvibe-io/memorymesh. Persistent, zero-dependency AI memory using SQLite. Local-first, cross-tool portable. This page covers its PyPI package (memorymesh).
Is the io.github.sparkvibe-io/memorymesh MCP server safe to use?
io.github.sparkvibe-io/memorymesh scores 30 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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.
Is the io.github.sparkvibe-io/memorymesh MCP server still maintained?
io.github.sparkvibe-io/memorymesh is still listed as active in the MCP registry. We last reached this channel on 4 November 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.sparkvibe-io/memorymesh MCP server under?
io.github.sparkvibe-io/memorymesh declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.