Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sphere Vault

REMOTE · MCP.GETSPHERE.XYZ

Sphere Vault: one encrypted vault for every AI you use

−12 this week 39 Trust /100

Last scanned (18 hours ago)

Scores higher than 35% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • 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.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (6)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • MCP protocol

Checks we could not complete (5)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)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 in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 −12
    • Stability: 0.03 → unverified ▼ security
    • 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. security
    • Tool coverage: fail → unverified ▼ functional
    • 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 functional
  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 +12
    • Authorization: pass → partial ▼ security
    • 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. security
    • Tool coverage: unverified → fail ▼ functional
    • Schema quality: unverified → 0 ▲ functional
    • 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 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.getsphere.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.getsphere.xyz CN=WR3,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 RSA 2048 SHA256-RSA 9dfaa1cf73325dbd12a1826d4ac824bb
SANs: mcp.getsphere.xyz
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.getsphere.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
getsphere.xyz. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.getsphere.xyz/mcp Verified 200
http (plaintext) http://mcp.getsphere.xyz/mcp HTTPS enforced
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

No tool schema has been captured from this endpoint yet.

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.

remote · mcp.getsphere.xyz

# add to Claude Code
claude mcp add --transport http xyz-getsphere-sphere-vault 'https://mcp.getsphere.xyz/mcp'
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.