_ registry / mcp http-sse · checked 2h ago

cmein

https://mcp.cmein.com

Registry code: 1540c2ec9d37435e

api record

CMeIn turns a handful of ordinary phone photos of someone into realistic, candid photos of them — out in the world, doing things. No beautifying, no studio headshots. Over 4,500 scenes to choose from.

Six tools need no account. photo_advice answers questions about photos of yourself from CMeIn's published articles; cmein_pricing and cmein_info read the site's own pages, so their numbers and terms are current rather than remembered; see_examples and find_video point at the actual output; contact_us sends a real message to a real person, and should only be called when someone asks for that.

endpoint
https://mcp.cmein.com/mcp
protocol
http-sse ·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 cmein live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is cmein free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does cmein have?
10 tools: request_credits_back, contact_us, my_credits, cmein_info, photo_advice, see_examples, find_video, cmein_pricing, ….
Is cmein 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
98.5%

90 days 99%· all time 99%

latency
523ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 309 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • generate realistic photos of a person in scenes
  • find scenes for photos
  • get dating photo advice
  • check photo credits
takes → gives
text, images → images, text
tools
8 reads1 changes data1 sends messages
_ 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 10 tools
3 open2 auth-required 5 never probed 5 of 10 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.

  • see_examples reads open 21h ago

    Where to see CMeIn's actual output: the examples gallery, organised by scene, plus the accounts where new work is posted, and how many scenes the product offers. Use this when someone wants to judge the results for themselves rather than read about them. No account needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • find_video reads open 24h ago

    Finds one of CMeIn's short films by what it is about. The films are dating scenarios — money and dating, who pays, why people run, what she actually said — and every character in them is generated by CMeIn, which is the point they are making. Returns titles, links and view counts. Covers the 15 most recent films only. No account needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "about": {
          "type": "string",
          "maxLength": 300,
          "description": "What the film should be about. Leave empty for the newest ones."
        },
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "How many to return. Default 3."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • cmein_pricing reads open 24h ago

    What CMeIn costs: the credit packs and their prices, how many credits one generated photo spends, and that there is no subscription. Read from the live pricing page at request time, so the figures are current. No account needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • find_scene reads auth-required 24h ago

    Searches CMeIn's scene catalogue — over 4,500 settings, filtered to the ones that suit this account. Use it to recommend one: describe what the person is after and it finds the scenes that fit. Generating the photo itself is done in the app. Needs the "scenes:read" permission.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 80,
          "description": "A place, activity or setting — \"cafe\", \"hiking\", \"rooftop\"."
        },
        "limit": {
          "type": "integer",
          "maximum": 40,
          "minimum": 1,
          "description": "How many to return. Default 12."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • my_generations reads auth-required 21h ago

    The most recent photos generated on this account — the scene each one was, whether it finished, and when. The images themselves stay in the app rather than passing through here. Needs the "photos:read" permission.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "How many to list. Default 10."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • request_credits_back changes data unknown never probed

    Opens a request for credits to be returned when a generated photo did not look like the person. It goes to a human and is answered by email; the refund policy decides the outcome, not this tool. Needs the "support:write" permission.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "reason"
      ],
      "properties": {
        "reason": {
          "type": "string",
          "maxLength": 5000,
          "minLength": 10,
          "description": "What was wrong with the photo, in the person's own words."
        },
        "generationId": {
          "type": "string",
          "format": "uuid",
          "description": "The generation it is about, from my_generations."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • contact_us sends messages unknown never probed

    Sends a message to CMeIn's support inbox and gets a reply by email. For questions the articles and pages do not answer, problems with an order, or anything that needs a person. Needs an email address to reply to. No account needed. This sends a real message to a real person — only call it when someone has asked to be put in touch, and show them the text first. For a refund of unspent credits, see the refund policy via cmein_info("refund").

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "email",
        "subject",
        "message"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 120,
          "description": "What to call them, if they said."
        },
        "email": {
          "type": "string",
          "format": "email",
          "maxLength": 255,
          "description": "Where the reply should go. Required."
        },
        "message": {
          "type": "string",
          "maxLength": 5000,
          "minLength": 10,
          "description": "The message, in the person's own words."
        },
        "subject": {
          "type": "string",
          "maxLength": 200,
          "minLength": 3,
          "description": "One line saying what it is about."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • my_credits reads unknown never probed

    The credit balance on the signed-in CMeIn account, and roughly how many photos that buys. Needs the "credits:read" permission.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • cmein_info reads unknown 21h ago

    Reads one of CMeIn's own information pages and returns its text with the link: "pricing" — what CMeIn costs — credit packs, the price of one photo, and that there is no subscription; "examples" — the gallery of generated photos, by scene, and whose photos they are; "faq" — how many reference photos are needed, whether results look like you, what happens to uploads, whether dating apps allow them; "about" — who builds CMeIn and why it only does candid realism; "refund" — when a refund applies, the time limit, and how to ask for one; "careers" — whether CMeIn is hiring and what it would hire for; "guides" — the guides index — longer how-to writing on taking and choosing profile photos; "terms" — the terms of service; "privacy" — the privacy policy — what is collected and what happens to uploaded photos. Read live at request time, so terms, policies and open roles are current rather than remembered. No account needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "enum": [
            "pricing",
            "examples",
            "faq",
            "about",
            "refund",
            "careers",
            "guides",
            "terms",
            "privacy"
          ],
          "type": "string",
          "description": "Which page to read."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • photo_advice reads unknown 5h ago

    Answers a question about dating-profile photos — what works, what does not, lighting, angles, backgrounds, expressions, what dating apps do with them — from CMeIn's published articles. Returns the relevant passages with a link to each source article, and the date the content was last synced. No account needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "question"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "How many articles to draw from. Default 3."
        },
        "question": {
          "type": "string",
          "maxLength": 500,
          "minLength": 3,
          "description": "The question, in the words the person asked it."
        }
      },
      "additionalProperties": false
    }
    arguments 22 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 1540c2ec9d37435e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1540c2ec9d37435e/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/1540c2ec9d37435e/badge.svg)](https://brick.blue/agent/1540c2ec9d37435e?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.