Servidor MCP de identifAI

• Nombre en el registronet.identifai/mcpverificado en el registro MCP

El nombre en el registro está bajo identifai.net. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-19
• Herramientas19
• El servidor se llamaidentifai-mcp-server
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-19 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 547 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta542 ms
• Espacio en el contexto del agente≈ 6504 tokenslas definiciones de todas sus herramientas (19), que el agente lleva en cada turno
• Definiciones de herramientasB · 83 de 100
• Resultados tipados0 de 19 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Sin indicar si solo lee o puede destruir: 19 de 19

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• classify_image

  Upload an image file to detect whether it is human-made or AI-generated. Provide the image content as a base64-encoded string. Returns a classification identifier for async result retrieval. WARNING: base64 encoding adds ~33% overhead to…

• classify_image_url

  Submit a publicly accessible image URL to detect whether it is human-made or AI-generated. Returns a classification identifier for result retrieval. Supports the same analysis options as file-based classification. Authentication: provide…

• get_image_classification

  Retrieve the classification result for a previously submitted image. Use the identifier returned by classify_image or classify_image_url. Poll this endpoint until the result is available.

• get_all_image_classifications

  Retrieve classification results for multiple images in a single request. Accepts up to 100 identifiers. Useful for batch result polling.

• get_classification_heatmap

  Retrieve a visual heatmap highlighting which regions of the image were detected as AI-generated. Requires the classification to have been submitted with withHeatmap enabled.

• override_image_classification

  Manually override the classification verdict for a previously classified image. Sets the result to either "human" or "artificial". Used for corrections and feedback.

• classify_video

  Upload a video file to detect whether it is human-made or AI-generated. Provide the video content as a base64-encoded string. The video is split into frames which are individually classified. Returns a classification identifier for async…

• classify_video_url

  Submit a publicly accessible video URL for AI-generated content detection. Supports the same frame extraction and analysis options as file-based classification. Authentication: provide your Identifai API key via the apiKey parameter or…

• get_video_classification

  Retrieve the classification result for a previously submitted video. Poll until the result is ready — video classification is always asynchronous.

• get_all_video_classifications

  Retrieve classification results for multiple videos in a single request. Accepts up to 100 identifiers.

• override_video_classification

  Manually override the classification verdict for a previously classified video. Sets the result to either "human" or "artificial".

• classify_audio

  Upload an audio or speech file to detect whether it is human-recorded or AI-synthesized. Provide the audio content as a base64-encoded string. Returns a classification identifier for async result retrieval. WARNING: base64 encoding adds…

• classify_audio_url

  Submit a publicly accessible audio URL for AI-generated speech detection. Returns a classification identifier for async result retrieval. Authentication: provide your Identifai API key via the apiKey parameter or configure the X-Api-Key…

• get_audio_classification

  Retrieve the classification result for a previously submitted audio file. Poll until the result is ready.

• get_all_audio_classifications

  Retrieve classification results for multiple audio files in a single request. Accepts up to 100 identifiers.

• override_audio_classification

  Manually override the classification verdict for a previously classified audio file. Sets the result to either "human" or "artificial".

• get_user_credits

  Retrieve the current available and used classification credits for the authenticated Identifai account. Use this to check quota status before submitting large batches.

• submit_tampering_tickets

  Submit one or more ticket images (as base64-encoded strings) to the Identifai v2 API for batch tampering detection. Each ticket is analysed independently; results are retrieved asynchronously via get_tampering_batch_results using the…

• get_tampering_batch_results

  Retrieve the tampering detection results for a previously submitted batch of tickets. Poll until the "done" field is true. Each result contains a verdict ("authentic" or "tampered") and per-heuristic verdicts.