Nexus Memory

com.chibitekPublished by chibitek.comOfficial publisherv0.1.0Updated Oct 24, 2026

Owner-scoped Nexus memory: search, facts, captures, KYC. Not Mochii's work graph.

The publisher's own server: Mochii work graph

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote Nexus memory server that gives an assistant owner-scoped access to search, facts, captures and KYC data through an OAuth-protected endpoint.

What you can do
  • Search an owner-scoped Nexus memory store.
  • Read and work with stored facts.
  • Access captures held in the memory.
  • Reach KYC-related records within the same owner scope.
When to use it
When you want an assistant to recall or look up information kept in a Nexus memory account, including facts, captures and KYC records, rather than starting from scratch each session.
Requirements
A remote streamable HTTP endpoint at api.nexus.chibitek.com; no local package or runtime is needed. OAuth authentication is required, so a Nexus account with the appropriate owner scope is needed. Network access to the endpoint is required.
Before you install
The server holds owner-scoped memory that includes KYC records, which is sensitive identity data; grant access only to accounts and assistants you trust. The description does not say whether tools can write, change or delete stored memory, so confirm that before use. No tool list or documentation was provided, so capabilities are known only at a high level.

Installation

In SourceWeft

  1. Open Nexus Memory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.chibitek%2Fnexus/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nexus-memory": {
      "type": "http",
      "url": "https://api.nexus.chibitek.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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 Chibitek integrations