PhotoSafe MCP server
com.eliteaiempire/photosafeeliteaiempire.comstreamable-httpv1.0.0Scanned
PhotoSafe backs up your photos encrypted on your own device, so nobody — including us — can look at
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.
What the PhotoSafe MCP server can do
The PhotoSafe MCP server is published by eliteaiempire.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: photosafe_about and photosafe_pricing), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
photosafe_aboutWhat 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.e…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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"}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
photosafe_pricingWhere 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://photosa…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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"}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
Only reads 2Show 2 read-only tools
photosafe_securityReturns the key-derivation rounds and labels from the crypto module, plus links to download the command-line client and the module source.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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"}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
usage_getUsage for the calling key (last 30 days)No findings
Why it is in this group
- The name "usage_get" says "get": a word for reading.
Description, as the server wrote it Usage for the calling key (last 30 days)
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 10, 2026, 08:23 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://photosafe.eliteaiempire.com/mcp: tools/list returned 4 tools to an anonymous client, including photosafe_about (write), photosafe_pricing (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http photosafe https://photosafe.eliteaiempire.com/mcpclaude mcp add --transport http photosafe https://photosafe.eliteaiempire.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__photosafe__photosafe_security",
"mcp__photosafe__usage_get"
],
"ask": [
"mcp__photosafe__photosafe_about",
"mcp__photosafe__photosafe_pricing"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as photosafe. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.eliteaiempire/photosafe/verify?hash=72fb4dd9fbc5f2c6f5417a857c9ba3772f54032ad714073106a94fd46608b861" | jq -e '.changed == false'Pinned hash 72fb4dd9fbc5, from Nov 9, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.eliteaiempire/photosafe/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.eliteaiempire/photosafe)Source: MCP Registry. Synced Nov 9, 2026, 17:17 UTC.
PhotoSafe MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PhotoSafe MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PhotoSafe MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PhotoSafe MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the PhotoSafe MCP server have?
- 4 tools: 2 write, 2 read. photosafe_about, photosafe_pricing, photosafe_security and usage_get.
Does the PhotoSafe MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PhotoSafe MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the PhotoSafe MCP server changed its tools?
- Not since anlyon.dev started tracking it. Last scanned Nov 9, 2026.