# DatePhotos.AI (remote · datephotos.ai)

Tinder, Hinge and Bumble photo rules and AI-photo policies, plus a free dating photo audit.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `datephotos.ai`: 85/100 (this document), [markdown](https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp.md), [page](https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp)

## Channel facts

- Endpoint: `https://datephotos.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-05.

- **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**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 253 tokens (~84/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DatePhotos.AI MCP server?

DatePhotos.AI is a hosted endpoint at https://datephotos.ai/api/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 ai-datephotos-datephotos 'https://datephotos.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-datephotos-datephotos": {
      "url": "https://datephotos.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-datephotos-datephotos": {
      "type": "http",
      "url": "https://datephotos.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-datephotos-datephotos]
url = "https://datephotos.ai/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-datephotos-datephotos --url 'https://datephotos.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-datephotos-datephotos:
    url: "https://datephotos.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-datephotos-datephotos": {
      "Transport": "http",
      "Url": "https://datephotos.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-datephotos-datephotos -t streamable-http -u 'https://datephotos.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-datephotos-datephotos": {
      "type": "http",
      "url": "https://datephotos.ai/api/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-04 (score 85, +1)

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

### 2026-11-02 (score 84, +1)

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

### 2026-10-31 (score 83, +1)

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

### 2026-10-28 (score 82, +1)

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

### 2026-10-26 (score 81, +1)

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

### 2026-10-24 (score 80, +1)

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

### 2026-10-22 (score 79, +1)

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

### 2026-10-20 (score 78, +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.

## MCP tools (3)

### `get_dating_app_photo_rules` (~77 tokens)

Dating app photo rules

Official photo rules for a dating app (Tinder, Hinge or Bumble): how many photos, how verification works, what is not allowed, and its AI-photo policy, with links to the official sources. Use when someone asks what photos a dating app allows or requires.

Input parameters:

- `app` (string, required): Which dating app

### `check_ai_photo_policy` (~81 tokens)

AI photo policy check

Whether Tinder, Hinge and Bumble allow AI-generated or AI-edited profile photos, how they detect them, what happens if you break the rules, and how to use AI photos safely — quoted from each app's official guidelines. Omit app to compare all three.

Input parameters:

- `app` (string): Optional: a single app; omit to compare all

### `audit_dating_photo` (~95 tokens)

Dating photo audit

Score one dating-profile photo 0-100 and list concrete issues and fixes (lighting, framing, face visibility, background, realism). Takes a public https URL to a JPEG/PNG/WebP image. Free: 5 audits per day per user. The photo is analysed and not stored.

Input parameters:

- `image_url` (string, required): Public https URL of the photo (JPEG, PNG or WebP, max 10 MB)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 80
- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75

## Common questions

### What is the DatePhotos.AI MCP server?

DatePhotos.AI is an MCP server listed in the public MCP registry as ai.datephotos/datephotos. Tinder, Hinge and Bumble photo rules and AI-photo policies, plus a free dating photo audit. This page covers its hosted endpoint (https://datephotos.ai/api/mcp).

### Is the DatePhotos.AI MCP server safe to use?

DatePhotos.AI scores 85 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 DatePhotos.AI MCP server expose?

DatePhotos.AI exposes 3 tools: get_dating_app_photo_rules, check_ai_photo_policy, audit_dating_photo. Their descriptions and schemas cost roughly 253 tokens of context every time the server is loaded.

### Does the DatePhotos.AI MCP server require authentication?

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

### Is the DatePhotos.AI MCP server still maintained?

DatePhotos.AI is still listed as active in the MCP registry. We last reached this channel on 5 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 DatePhotos.AI MCP server?

VerifyMCP ran 13 checks on DatePhotos.AI, 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://datephotos.ai/api/mcp
- Website: https://datephotos.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-datephotos-datephotos/api-mcp