Unabyss

com.unabyssPublished by unabyss.comOfficial publisherv1.0.0Updated Oct 29, 2026

Shared memory for every AI tool you use.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Unabyss is a remote MCP server that provides shared memory across the AI tools a user works with.

What you can do
  • The registry description is a single line: shared memory for every AI tool you use.
  • No tool list, instructions or README is published, so the specific memory operations (such as saving, recalling or syncing context) cannot be confirmed from the available information.
  • What is known is that it is a hosted remote endpoint reached over streamable HTTP with OAuth sign-in.
When to use it
Consider it when you want several AI assistants or tools to draw on one common memory rather than each keeping its own context. Because the published details are minimal, check the provider's own documentation before relying on it for anything important.
Requirements
A remote MCP endpoint at mcp.unabyss.com over streamable HTTP, with OAuth authentication required. No environment variables, headers or local packages are declared, so no local runtime is needed.
Before you install
OAuth grants the server access to an account, and a shared memory service stores whatever context is written to it, potentially across multiple AI tools. The published material does not describe what is stored, who can read it, or how it is retained, so review the provider's privacy and data-handling terms before connecting.

Installation

In SourceWeft

  1. Open Unabyss 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.unabyss%2Funabyss/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": {
    "unabyss": {
      "type": "http",
      "url": "https://mcp.unabyss.com/"
    }
  }
}

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. v1.0.0LatestOct 29, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.