incarn
Registry code: 5a58294c89166091
Animate old family photos into short lifelike videos with AI.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.incarn.co/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 incarn live?
- Yes — it answered the hub's last check (checked 16m ago). It answered 100% of checks over the last 30 days.
- Is incarn free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does incarn have?
- 5 tools: confirm_upload, create_upload, animate_photo, list_examples, get_animation_status.
- Is incarn 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.6%· all time 99.6%
last good check
of 5 tools
- degraded → live
- degraded → live
- live → degraded· HTTP 502
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- media generation video
- used for
- animate an old family photo into a video
- upload a photo for animation
- check an animation job status
- view before and after examples
- takes → gives
- images → video
- tools
- 2 reads3 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_examples reads open 19h ago
Voir des exemples avant/après d'animation de photos anciennes (galerie de démonstration).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "beat": { "type": "string", "description": "Thème optionnel (ex: 'mariage', 'bébé', 'portrait')." } }, "additionalProperties": false }arguments 11 linesget_animation_status reads auth-required 19h ago
Récupère le statut d'un job d'animation et l'URL de la vidéo une fois prête.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "job_id" ], "properties": { "job_id": { "type": "string", "description": "Identifiant du job d'animation." } }, "additionalProperties": false }arguments 14 linesconfirm_upload changes data unknown never probed
Étape 2 : une fois les octets envoyés (PUT) sur l'upload_url, appelle-moi avec le upload_id pour valider la photo (modération incluse). Renvoie un photo_id à passer à animate_photo.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "upload_id" ], "properties": { "upload_id": { "type": "string", "description": "Le upload_id renvoyé par create_upload." } }, "additionalProperties": false }arguments 14 linescreate_upload changes data unknown never probed
Étape 1 pour animer une photo JOINTE dans le chat quand il n'y a pas d'URL publique. Renvoie une URL d'upload : PUT les octets du fichier dessus (en-tête Content-Type), puis confirm_upload. IMPORTANT : si une URL publique de la photo existe, préfère plutôt animate_photo avec image_url (aucun upload, marche partout). Le PUT peut être refusé par l'egress d'un agent sandboxé (403 'host_not_allowed') : dans ce cas ne le retente pas, bascule sur image_url ou fais autoriser api.incarn.co. N'envoie JAMAIS l'image en base64.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mime_type" ], "properties": { "mime_type": { "type": "string", "description": "Type MIME de l'image (ex: 'image/jpeg', 'image/png')." } }, "additionalProperties": false }arguments 14 linesanimate_photo changes data unknown never probed
Anime une photo ancienne en une courte vidéo naturelle. Consomme 1 crédit (compte approvisionné requis, pas d'essai gratuit). Abonnement à partir de 19 €/mois HT, soit 0,76 € la photo, sur https://www.incarn.co/developers. Fournis l'image via image_url (URL publique http(s) — PRÉFÉRÉ : notre serveur va la chercher, marche partout, aucun upload côté client) OU image_file (fichier joint par l'utilisateur, rempli automatiquement par ChatGPT) OU photo_id (create_upload puis confirm_upload ; ce PUT peut être bloqué dans un agent sandboxé). Privilégie image_url dès qu'une URL est disponible. À n'utiliser que pour des photos que l'utilisateur a le droit d'animer (les siennes, sa famille, ses ancêtres) ; refuse d'animer des personnalités publiques identifiables ou des personnes tierces sans leur consentement.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "style": { "type": "string", "description": "Indication libre et subtile sur le mouvement (optionnel)." }, "photo_id": { "type": "string", "description": "Photo uploadée (via confirm_upload), si l'utilisateur a joint un fichier sans URL. Prioritaire si fourni." }, "image_url": { "type": "string", "format": "uri", "description": "URL publique http(s) de la photo. Chemin PRÉFÉRÉ (aucun upload, marche partout)." }, "image_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string", "description": "Identifiant du fichier côté hôte." }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "URL de téléchargement de l'image, fournie par l'hôte." } }, "description": "Fichier joint par l'utilisateur — rempli AUTOMATIQUEMENT par ChatGPT (openai/fileParams) quand une photo est attachée. Notre serveur télécharge le download_url côté serveur (aucun upload côté client).", "additionalProperties": false } }, "additionalProperties": false }arguments 45 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 id5a58294c89166091.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5a58294c89166091/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5a58294c89166091?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.