mimicly
Registry code: dd74ba8bdc574fd7
Mimicly turns a conversation into a chat mockup inside a messaging or AI chat template. list_templates returns the template ids; create_chat_mockup takes one of them and the conversation. The result has a watermarked preview image and an "Open in Mimicly editor" link where the user finishes, exports or records the scene. Scenes are fictional and written by the user. The server refuses scenes that pose as a real person, company or institution, or that could pass as real evidence of a conversation.
- endpoint
- https://mimicly.net/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 mimicly live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is mimicly free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does mimicly have?
- 2 tools: create_chat_mockup, list_templates.
- Is mimicly 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.
90 days 99.7%· all time 99.7%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- topic
- media generation images
- used for
- create a chat conversation mockup
- list chat templates
- takes → gives
- text, data → images, text
- tools
- 1 reads1 changes data
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.
through this hub
successful
what callers paid
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.
list_templates reads open 20h ago
Lists the chat templates Mimicly can fill in: messaging apps (for example WhatsApp, iMessage, Telegram, Discord) and AI chat apps (for example ChatGPT, Claude, Gemini). Returns each template id, display name, category, whether it can be recorded as an animated video in Mimicly, and whether clean export needs Mimicly Pro. Call it when you are not sure which template id to pass to create_chat_mockup.
{ "type": "object", "properties": { "category": { "enum": [ "messages", "ai-chat" ], "type": "string", "description": "Optional filter. \"messages\" for messaging apps, \"ai-chat\" for AI assistant chats." } } }arguments 13 linescreate_chat_mockup changes data unknown never probed
Builds a chat mockup in a Mimicly template from a conversation the user wants, for a story, video, lesson, design, presentation or demo. Returns a watermarked preview image URL, an "Open in Mimicly editor" URL where the user can edit, export or record the scene, and the Mimicly iOS App Store link. Scenes are fictional mockups written by the user. The tool is not for posing as a real person, company or institution, for making a chat look like real evidence, or for misleading someone, and the server refuses such scenes. Limits: up to 30 messages and 4000 characters in total. Messages cannot contain links, login or verification codes, passwords, or payment or account details. Nothing is posted or saved to an account. Links stop working after 30 days.
{ "type": "object", "required": [ "template", "messages" ], "properties": { "theme": { "enum": [ "light", "dark" ], "type": "string", "description": "Optional light or dark appearance. Defaults to the template default." }, "title": { "type": "string", "maxLength": 80, "description": "Optional scene title, for example \"Weekend plans\". Used as the group or conversation name when the template shows one." }, "me_name": { "type": "string", "maxLength": 40, "minLength": 1, "description": "Optional display name for the user's own messages. Defaults to \"You\"." }, "messages": { "type": "array", "items": { "type": "object", "required": [ "from", "text" ], "properties": { "from": { "type": "string", "maxLength": 40, "minLength": 1, "description": "\"me\" for the user's messages, \"them\" for the other person, or one of the participant names in a group chat. In AI chat templates, \"me\" is the prompt and anything else is the assistant reply." }, "text": { "type": "string", "maxLength": 500, "minLength": 1, "description": "Message text, up to 500 characters. Plain text; links are not accepted." }, "time": { "type": "string", "maxLength": 12, "description": "Optional timestamp label shown on the message, for example \"9:41 AM\"." } } }, "maxItems": 30, "minItems": 1, "description": "Conversation in order, 1 to 30 messages, at most 4000 characters in total." }, "template": { "type": "string", "maxLength": 64, "minLength": 1, "description": "Template id from list_templates, for example \"whatsapp\", \"imessage\" or \"chatgpt\"." }, "participants": { "type": "array", "items": { "type": "string", "maxLength": 40, "minLength": 1 }, "maxItems": 8, "description": "Display names of the other people in the chat, not the user. Use made-up or user-provided names. Ignored by AI chat templates." } } }arguments 76 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's iddd74ba8bdc574fd7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dd74ba8bdc574fd7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dd74ba8bdc574fd7?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.