Void Os

io.github.demos-raPublished by GitHub account demos-rav0.1.0Updated Oct 24, 2026

Memory for AI agents: a data bank of MTSV relations, read through one tool.

The publisher's own server: void.bible

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Gives an AI assistant a memory data bank of MTSV relations, read through a single tool.

What you can do
Void Os is a local MCP server that provides memory for AI agents. According to its registry description, it holds a data bank of MTSV relations that the assistant reads through one tool. No individual tools are listed in the manifest, so the exact read operations are not documented here.
When to use it
Consider it when an assistant needs a persistent store of relations to recall context across sessions. It is a desktop-only local process, so it suits a single machine rather than a shared or hosted setup. Because the tool surface is undocumented, evaluate it only if you can inspect the package first.
Requirements
Runs as a local process over stdio on the user's machine; desktop only, not available as a web executable. Distributed as an npm package (void-os) and a PyPI package (void-os), so a Node.js or Python runtime is needed depending on which you install. No authentication, environment variables, or headers are declared.
Before you install
No credentials, secrets, or network access are declared, and no tools are listed, so the read and write behavior cannot be verified from the manifest. The description says relations are read through one tool, but whether the server also stores or changes data is not stated. Inspect the package before installing, and treat any memory it holds as data the assistant can surface.

Installation

In SourceWeft

  1. Open Void Os in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Void integrations