Incarn
REMOTE · API.INCARN.CO · SCANNED SEP 20
Animate old family photos into short lifelike videos with AI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 684 tokens (~114/item across 6 items; 5 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the Incarn MCP server?
Incarn is a hosted endpoint at https://api.incarn.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.incarn.co
claude mcp add --transport http co-incarn-photo-animation 'https://api.incarn.co/mcp'
{
"mcpServers": {
"co-incarn-photo-animation": {
"url": "https://api.incarn.co/mcp"
}
}
} {
"servers": {
"co-incarn-photo-animation": {
"type": "http",
"url": "https://api.incarn.co/mcp"
}
}
} [mcp_servers.co-incarn-photo-animation] url = "https://api.incarn.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-incarn-photo-animation": {
"type": "remote",
"url": "https://api.incarn.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-incarn-photo-animation --url 'https://api.incarn.co/mcp' --transport streamable-http
mcp_servers:
co-incarn-photo-animation:
url: "https://api.incarn.co/mcp" {
"McpServers": {
"co-incarn-photo-animation": {
"Transport": "http",
"Url": "https://api.incarn.co/mcp"
}
}
} assistant mcp add co-incarn-photo-animation -t streamable-http -u 'https://api.incarn.co/mcp'
{
"mcpServers": {
"co-incarn-photo-animation": {
"type": "http",
"url": "https://api.incarn.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
- Tool “animate_photo” rewrote its description, which is the text the model reads security
- Server version: 0.1.0 → 1.1.0 functional
- 8 Sept 26 +1
- Tool “animate_photo” rewrote its description, which is the text the model reads security
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.incarn.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=incarn.co | CN=YE2,O=Let's Encrypt,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 55897a16f0f96d77c55d39cf8cd7de4fb74 |
| SANs: *.incarn.co, incarn.co | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.incarn.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| incarn.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.incarn.co/.well-known/oauth-protected-resource", scope="mcp"
Bearer resource_metadata="https://api.incarn.co/.well-known/oauth-protected-resource", scope="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Document | https://api.incarn.co/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.incarn.co/mcp |
| Authorisation server | https://api.incarn.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.incarn.co/mcp | Verified | 200 | |
| http (plaintext) | http://api.incarn.co/mcp | HTTPS enforced | 308 | https://api.incarn.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
animate_photo Animer une photo ~338
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.
| Name | Type | Req | Description |
|---|---|---|---|
| image_file | object | – | 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). |
| image_url | string | – | URL publique http(s) de la photo. Chemin PRÉFÉRÉ (aucun upload, marche partout). |
| photo_id | string | – | Photo uploadée (via confirm_upload), si l'utilisateur a joint un fichier sans URL. Prioritaire si fourni. |
| style | string | – | Indication libre et subtile sur le mouvement (optionnel). |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Identifiant du job d'animation (à poller). |
| photo_url | string|null | yes | URL de la photo source (avant), pour l'aperçu inline. |
| status | string | yes | Statut du job : en cours, réussi ou échoué. |
| video_url | string|null | yes | URL de la vidéo une fois prête, sinon null. |
No examples provided.
confirm_upload Finaliser un upload de photo ~74
É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.
| Name | Type | Req | Description |
|---|---|---|---|
| upload_id | string | yes | Le upload_id renvoyé par create_upload. |
| Name | Type | Req | Description |
|---|---|---|---|
| photo_id | string | yes | Identifiant de la photo, à passer à animate_photo. |
No examples provided.
create_upload Préparer un upload de photo ~167
É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.
| Name | Type | Req | Description |
|---|---|---|---|
| mime_type | string | yes | Type MIME de l'image (ex: 'image/jpeg', 'image/png'). |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in | number | yes | Validité de l'URL, en secondes. |
| note | string | yes | Marche à suivre + fallback si le PUT est bloqué. |
| upload_id | string | yes | À passer à confirm_upload. |
| upload_url | string | yes | URL sur api.incarn.co : PUT les octets du fichier dessus. |
No examples provided.
get_animation_status Statut d'une animation ~47
Récupère le statut d'un job d'animation et l'URL de la vidéo une fois prête.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Identifiant du job d'animation. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string|null | yes | Message d'erreur si le job a échoué, sinon null. |
| id | string | yes | Identifiant du job. |
| photo_url | string|null | yes | URL de la photo source (avant), pour l'aperçu inline. |
| status | string | yes | Statut du job : en cours, réussi ou échoué. |
| video_url | string|null | yes | URL de la vidéo une fois prête, sinon null. |
No examples provided.
list_examples Exemples d'animations ~53
Voir des exemples avant/après d'animation de photos anciennes (galerie de démonstration).
| Name | Type | Req | Description |
|---|---|---|---|
| beat | string | – | Thème optionnel (ex: 'mariage', 'bébé', 'portrait'). |
| Name | Type | Req | Description |
|---|---|---|---|
| beat | string|null | yes | Thème appliqué, ou null. |
| examples | array | yes | Liste d'exemples avant/après. |
| gallery_url | string | yes | URL de la galerie publique où chaque portrait s'anime (avant/après). À partager avec l'utilisateur. |
No examples provided.
What is the Incarn MCP server?
Incarn is an MCP server listed in the public MCP registry as co.incarn/photo-animation. Animate old family photos into short lifelike videos with AI. This page covers its hosted endpoint (https://api.incarn.co/mcp).
Is the Incarn MCP server safe to use?
Incarn scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Incarn MCP server expose?
Incarn exposes 5 tools: list_examples, create_upload, confirm_upload, animate_photo, get_animation_status. Their descriptions and schemas cost roughly 679 tokens of context every time the server is loaded.
Does the Incarn MCP server require authentication?
Yes. Incarn asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Incarn MCP server still maintained?
Incarn is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.