# Sphere Vault (remote · mcp.getsphere.xyz)

Sphere Vault: one encrypted vault for every AI you use

- Trust score: 39/100 (low)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.getsphere.xyz`: 39/100 (this document), [markdown](https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp.md), [page](https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp)

## Channel facts

- Endpoint: `https://mcp.getsphere.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Sphere Vault MCP server?

Sphere Vault is a hosted endpoint at https://mcp.getsphere.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xyz-getsphere-sphere-vault 'https://mcp.getsphere.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-getsphere-sphere-vault": {
      "url": "https://mcp.getsphere.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-getsphere-sphere-vault": {
      "type": "http",
      "url": "https://mcp.getsphere.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-getsphere-sphere-vault]
url = "https://mcp.getsphere.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-getsphere-sphere-vault": {
      "type": "remote",
      "url": "https://mcp.getsphere.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-getsphere-sphere-vault --url 'https://mcp.getsphere.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-getsphere-sphere-vault:
    url: "https://mcp.getsphere.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-getsphere-sphere-vault": {
      "Transport": "http",
      "Url": "https://mcp.getsphere.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-getsphere-sphere-vault -t streamable-http -u 'https://mcp.getsphere.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-getsphere-sphere-vault": {
      "type": "http",
      "url": "https://mcp.getsphere.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-20 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-19 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-18 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-17 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-16 (score 39, −12)

- [security regression] Stability: 0.03 → unverified
- [security regression] Authorization: partial → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional regression] Tool coverage: fail → unverified
- [functional regression] Schema quality: 0 → unverified
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-15 (score 51, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 51, +12)

- [security regression] Authorization: pass → partial
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Injection markers: Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.
- [functional regression] Tool coverage: unverified → fail
- [functional improvement] Schema quality: unverified → 0
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Destructive annotations: unverified
- [functional] First check of Schema quality: poor
- [functional] First check of Schema quality: unverified
- [functional] First check of Schema quality: pass

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp#diagnostics

## Score history

- 2026-11-21: 39
- 2026-11-20: 39
- 2026-11-19: 39
- 2026-11-18: 39
- 2026-11-17: 39
- 2026-11-16: 39
- 2026-11-15: 51
- 2026-11-14: 51
- 2026-11-13: 39
- 2026-11-12: 39
- 2026-11-11: 39
- 2026-11-10: 39
- 2026-11-09: 39
- 2026-11-08: 39
- 2026-11-07: 39
- 2026-11-06: 39
- 2026-11-05: 39

## Common questions

### What is the Sphere Vault MCP server?

Sphere Vault is an MCP server listed in the public MCP registry as xyz.getsphere/sphere-vault. Sphere Vault: one encrypted vault for every AI you use. This page covers its hosted endpoint (https://mcp.getsphere.xyz/mcp).

### Is the Sphere Vault MCP server safe to use?

Sphere Vault scores 39 out of 100 on VerifyMCP. 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.

### Does the Sphere Vault MCP server require authentication?

No. We connected to Sphere Vault without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sphere Vault MCP server still maintained?

Sphere Vault is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Sphere Vault MCP server?

VerifyMCP ran 6 checks on Sphere Vault, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 2 more. 5 items could not be completed, a gap on our side rather than a finding about Sphere Vault: Authorization, Schema quality, Stability, Tool coverage and 1 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.getsphere.xyz/mcp
- Repository: https://github.com/lgcy-official/spheremaster
- Website: https://getsphere.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-getsphere-sphere-vault/mcp
