Sphere Vault

xyz.getspherePublished by getsphere.xyzOfficial publisherv1.0.0Updated Nov 5, 2026

Sphere Vault: one encrypted vault for every AI you use

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Sphere Vault is a remote MCP endpoint that gives AI assistants access to a single encrypted vault shared across the AI tools you use.

What you can do
  • The listing names no tools, so capabilities are only broadly described.
  • It presents one encrypted vault intended to be shared across multiple AI assistants.
  • Assistants connect to it as a remote endpoint over streamable HTTP.
  • Access is gated by OAuth sign-in.
When to use it
Consider it if you want several AI assistants to draw on the same encrypted vault rather than separate per-tool storage. The listing gives no detail on what the vault holds or which operations are exposed, so check the provider's documentation before relying on it.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP, plus an OAuth sign-in with the provider. No packages, environment variables or headers are declared.
Before you install
The vault is described as encrypted and shared across every AI you use, so anything stored in it may be readable by each connected assistant. OAuth grants the server access to your account; review the scopes requested. The listing does not say what data is stored or sent to third parties.

Installation

In SourceWeft

  1. Open Sphere Vault 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/xyz.getsphere%2Fsphere-vault/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": {
    "sphere-vault": {
      "type": "http",
      "url": "https://mcp.getsphere.xyz/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. v1.0.0LatestNov 5, 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.