# PhotoSafe (remote · photosafe.eliteaiempire.com)

PhotoSafe backs up your photos encrypted on your own device, so nobody — including us — can look at

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `photosafe.eliteaiempire.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe.md), [page](https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe)

## Channel facts

- Endpoint: `https://photosafe.eliteaiempire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 615 tokens (~76/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the PhotoSafe MCP server?

PhotoSafe is a hosted endpoint at https://photosafe.eliteaiempire.com/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 com-eliteaiempire-photosafe 'https://photosafe.eliteaiempire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-eliteaiempire-photosafe": {
      "url": "https://photosafe.eliteaiempire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-eliteaiempire-photosafe": {
      "type": "http",
      "url": "https://photosafe.eliteaiempire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-eliteaiempire-photosafe]
url = "https://photosafe.eliteaiempire.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-eliteaiempire-photosafe": {
      "type": "remote",
      "url": "https://photosafe.eliteaiempire.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-eliteaiempire-photosafe --url 'https://photosafe.eliteaiempire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-eliteaiempire-photosafe:
    url: "https://photosafe.eliteaiempire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-eliteaiempire-photosafe": {
      "Transport": "http",
      "Url": "https://photosafe.eliteaiempire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-eliteaiempire-photosafe -t streamable-http -u 'https://photosafe.eliteaiempire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-eliteaiempire-photosafe": {
      "type": "http",
      "url": "https://photosafe.eliteaiempire.com/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-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 72, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] Schema quality: 62 → 76
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.27
- [functional] First check of Tool coverage: 100
- [functional] New tool “get_checkout_link”
- [functional] New tool “get_company_info”
- [functional] New tool “list_pricing”
- [functional] New tool “search_site”

### 2026-11-16 (score 71, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `photosafe_security` (~89 tokens)

Returns the key-derivation rounds and labels from the crypto module, plus links to download the command-line client and the module source. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

### `photosafe_about` (~70 tokens)

What PhotoSafe does and what is free Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

### `photosafe_pricing` (~70 tokens)

Where prices live and what costs nothing Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

### `get_company_info` (~72 tokens)

Company, product, contact page and policy links. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

### `list_pricing` (~89 tokens)

Every plan with monthly and yearly price in USD cents and dollars. Yearly is 10x monthly. Matches the /pricing page. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

### `get_checkout_link` (~120 tokens)

Returns a hosted Stripe Checkout URL (cs_live_) for plan safe, vault or family, monthly or yearly. Falls back to the pricing page URL when checkout is unavailable. Nothing is charged until a person pays. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

Input parameters:

- `period` (string): period
- `plan` (string): plan

### `search_site` (~86 tokens)

Keyword search over the public pages; returns title, url and a one-line summary. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://photosafe.eliteaiempire.com/pricing"}.

Input parameters:

- `query` (string, required): query

### `usage_get` (~19 tokens)

Usage for the calling key (last 30 days)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 68
- 2026-11-09: 68

## Common questions

### What is the PhotoSafe MCP server?

PhotoSafe is an MCP server listed in the public MCP registry as com.eliteaiempire/photosafe. PhotoSafe backs up your photos encrypted on your own device, so nobody, including us, can look at. This page covers its hosted endpoint (https://photosafe.eliteaiempire.com/mcp).

### Is the PhotoSafe MCP server safe to use?

PhotoSafe scores 74 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.

### What tools does the PhotoSafe MCP server expose?

PhotoSafe exposes 8 tools: photosafe_security, photosafe_about, photosafe_pricing, get_company_info, list_pricing, and 3 more. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Does the PhotoSafe MCP server require authentication?

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

### Is the PhotoSafe MCP server still maintained?

PhotoSafe 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 PhotoSafe MCP server?

VerifyMCP ran 13 checks on PhotoSafe, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://photosafe.eliteaiempire.com/mcp
- Website: https://photosafe.eliteaiempire.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe.json
- HTML version of this page: https://verifymcp.io/servers/com-eliteaiempire-photosafe/photosafe
