General Tools
datephotos.ai
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://datephotos.ai/api/mcp
MCP server metadata
- Name
- datephotos
- Version
- 0.1.0
Known tools 3
get_dating_app_photo_rulesOfficial 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.
Inferred read-onlycheck_ai_photo_policyWhether 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.
Inferred read-onlyaudit_dating_photoScore one dating-profile photo 0-100 and list concrete issues and fixes (lighting, framing, face visibility, background, realism).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.datephotos]
url = "https://datephotos.ai/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"datephotos": {
"type": "http",
"url": "https://datephotos.ai/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: datephotos
Remote MCP URL: https://datephotos.ai/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"datephotos": {
"url": "https://datephotos.ai/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"datephotos": {
"type": "http",
"url": "https://datephotos.ai/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "datephotos",
"transport": "streamable-http",
"url": "https://datephotos.ai/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.