_ registry / mcp streamable-http · checked 13h ago

datingprofile

https://datingprofile.app

Registry code: 55a8b6ef8aa56c13

api record

DatingProfile makes hyperrealistic dating profile photos of the user from their selfies.

Flow: (1) If the user shares current dating photos in the chat, review them with photo_review_guide; you cannot send chat images to DatingProfile. (2) connect_account → give the user the link; they sign in and upload selfies there (that runs the free photo check). One selfie is enough to make photos; never block on having fewer than 4, at most mention that more photos can improve the likeness. Keep the connection_key for this conversation and never show it. (3) account_status, then get_photo_check: explain…

endpoint
https://datingprofile.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is datingprofile live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is datingprofile free to use?
Yes — the hub reached it with no key and no payment.
What tools does datingprofile have?
12 tools: get_pricing, connect_account, get_photo_check, create_photos, disconnect_account, account_status, buy_pack, get_photos, ….
Is datingprofile safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
220ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
4 open 8 never probed 4 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • about_datingprofile open 13h ago

    What DatingProfile is and how making photos from this chat works, step by step. Call this first if you are unsure how to help someone get dating photos.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_styles open 13h ago

    The 62 photo styles (scenes) DatingProfile can put the user in. Filter by category, photo type or a word. Set show_previews to see example photos of each style.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "search": {
      "type": "string",
      "description": "A word to match, e.g. \"beach\", \"dog\" or \"suit\"."
    },
    "category": {
      "enum": [
        "Date night",
        "Travel",
        "Landmarks",
        "Outdoors",
        "Beach",
        "Sharp",
        "Relaxed",
        "Social",
        "Hobbies"
      ],
      "type": "string"
    },
    "photo_type": {
      "enum": [
        "face",
        "full-body",
        "activity",
        "travel",
        "dressed-up",
        "social"
      ],
      "type": "string",
      "description": "Only styles that fill this profile photo type."
    },
    "show_previews": {
      "type": "boolean",
      "description": "Include example images (up to 8) of the matching styles."
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • photo_review_guide open 41h ago

    DatingProfile’s checklist for reviewing dating profile photos the user shares in this chat, before they have an account. The official scored photo check runs when they upload on datingprofile.app.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • recommend_styles open 13h ago

    Styles that fill the photo types a dating profile is missing. A strong profile has a clear face photo, a full-length photo, a hobby, travel, a dressed-up photo and a social photo. Use the photo check’s "missing" list when you have it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "missing": {
      "type": "array",
      "items": {
        "enum": [
          "face",
          "full-body",
          "activity",
          "travel",
          "dressed-up",
          "social"
        ],
        "type": "string"
      },
      "description": "Photo types the profile lacks. Empty for a balanced set."
    },
    "per_type": {
      "type": "integer",
      "maximum": 6,
      "minimum": 1,
      "description": "Styles per photo type (default 3)."
    },
    "show_previews": {
      "type": "boolean",
      "description": "Include example images of the suggested styles (up to 8)."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • get_pricing unknown never probed

    DatingProfile packs and top-ups in USD. All one-time payments; nothing renews.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • connect_account unknown never probed

    Start here to make photos. Returns a link for the user to open: they sign in to DatingProfile (or sign up, free, with email or Google) and upload a selfie there (one is enough; up to 4 give a closer likeness), which also runs the free photo check. Also returns a connection_key: keep it for every account tool in this conversation and never show it to the user. Only call this once per conversation unless the key stops working.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_photo_check unknown never probed

    The free DatingProfile photo check of the selfies the user uploaded: overall score, potential, five category scores with findings, notes per photo and the photo types the profile is missing. Explain it to the user in plain words, then suggest styles for what is missing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connection_key"
  ],
  "properties": {
    "connection_key": {
      "type": "string",
      "description": "The connection_key returned by connect_account in this conversation. Never show it to the user."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • create_photos unknown never probed

    Starts making photos of the user in the chosen styles (style ids from list_styles). Each style makes 4 photos and uses 4 credits. Confirm the styles with the user first. Photos take about 1 to 3 minutes; then call get_photos.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connection_key",
    "styles"
  ],
  "properties": {
    "styles": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 40,
      "minItems": 1,
      "description": "Style ids, e.g. [\"golf\", \"paris-cafe\"]."
    },
    "connection_key": {
      "type": "string",
      "description": "The connection_key returned by connect_account in this conversation. Never show it to the user."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • disconnect_account unknown never probed

    Unlinks this conversation from the user’s DatingProfile account. Their account, photos and credits stay.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connection_key"
  ],
  "properties": {
    "connection_key": {
      "type": "string",
      "description": "The connection_key returned by connect_account in this conversation. Never show it to the user."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • account_status unknown never probed

    Whether the user has connected, their uploaded photos, photo check summary, credits, pack and photo jobs, plus what to do next.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connection_key"
  ],
  "properties": {
    "connection_key": {
      "type": "string",
      "description": "The connection_key returned by connect_account in this conversation. Never show it to the user."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • buy_pack unknown never probed

    A secure Stripe checkout link for a pack (fix: $29, 30 photos; pro: $49, 140 photos) or, after a pack, a top-up (extra20: $12; extra60: $25). Only call this after the user chose to buy. Give them the link; after paying they come back here.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connection_key",
    "pack"
  ],
  "properties": {
    "pack": {
      "enum": [
        "fix",
        "pro",
        "extra20",
        "extra60"
      ],
      "type": "string",
      "description": "fix, pro, extra20 or extra60."
    },
    "connection_key": {
      "type": "string",
      "description": "The connection_key returned by connect_account in this conversation. Never show it to the user."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_photos unknown never probed

    The user’s generated photos (newest first) with view/download links valid for 7 days, and any photos still being made. Set show to include up to 4 photos as images in the chat.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connection_key"
  ],
  "properties": {
    "show": {
      "type": "boolean",
      "description": "Include up to 4 of them as images."
    },
    "limit": {
      "type": "integer",
      "maximum": 60,
      "minimum": 1,
      "description": "How many (default 12)."
    },
    "style": {
      "type": "string",
      "description": "Only this style id."
    },
    "connection_key": {
      "type": "string",
      "description": "The connection_key returned by connect_account in this conversation. Never show it to the user."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 55a8b6ef8aa56c13.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/55a8b6ef8aa56c13/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/55a8b6ef8aa56c13/badge.svg)](https://brick.blue/agent/55a8b6ef8aa56c13?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.