Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
VerifEye Face API: Identify (apparent age, gender, emotions, attention), Onboard and Compare faces.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://verifeye-mcp-server.realeyes.ai/mcpEjecuta esto en tu terminal
claude mcp add --transport http verifeye https://verifeye-mcp-server.realeyes.ai/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"verifeye": {
"url": "https://verifeye-mcp-server.realeyes.ai/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"verifeye": {
"type": "http",
"url": "https://verifeye-mcp-server.realeyes.ai/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://verifeye-mcp-server.realeyes.ai/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
El servidor pide iniciar sesión antes de mostrar sus herramientas.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 9 nov 2026
El nombre en el registro se verificó con el dominio realeyes.ai (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 403 ms (HTTP 401)
Necesita una clave o un token que debes copiar y pegar a mano
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 2 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.1.1) llegó al registro hace 23 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Joe Hill, AI partner in Tennessee
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Check open times and book a free 15-minute fit call with Joe Hill, or ask Harvey about his work.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
The VerifEye MCP Server is a remotely hosted Model Context Protocol (MCP) server from Realeyes. It exposes the VerifEye Face API as tools an AI assistant can call: analyze a face for apparent age and gender plus momentary emotions and attention (Identify), onboard a face so the same person is identified later (Onboard), compare an image against one onboarded face (Compare), and manage the collections onboarded faces live in.
The server is hosted by Realeyes, so there is nothing to install or run. This repository holds its public listing metadata for MCP registries: server.json.
Full documentation: https://verifeye-docs.realeyes.ai/verifeye-apis/mcp-server/
https://verifeye-mcp-server.realeyes.ai/mcp
Transport: Streamable HTTP. This is the server's only address. If a registry or directory lists a different one, do not connect to it, and contact us.
The server uses OAuth 2.1 (authorization code with PKCE). When you connect, a VerifEye sign-in and consent screen opens in your browser. You never put an API key into your MCP client: your account's API key is resolved on the server side and is never exposed to the client.
The server offers no dynamic client registration. ChatGPT, VS Code and Codex identify themselves with a Client ID Metadata Document, so there is nothing to enter. Claude, Claude Code, Cursor and the Gemini CLI use a pre-registered client ID.
Step-by-step setup for Claude Code, Claude, ChatGPT, VS Code, Cursor, the Gemini CLI and Codex, including the client ID each one needs, is in the documentation: Connecting a client.
For example, in VS Code add .vscode/mcp.json to your project root:
{
"servers": { "verifeye": { "type": "http", "url": "https://verifeye-mcp-server.realeyes.ai/mcp" } } }
Start the server from the MCP: List Servers command, then sign in when the browser opens.
Once the server is connected and you have signed in, ask in plain language and the assistant picks the tools.
Give the image as a link. The image tools take a public URL of a JPEG or PNG image, which VerifEye fetches itself. An image attached to the conversation cannot be passed to a tool, so put the image somewhere reachable and give the assistant that link. Prefer a pre-signed link that expires in minutes to a durably public URL. Where the server offers verifeye_get_upload_url and your client can make HTTPS requests of its own, the client can upload the image instead. Image requirements: documentation.
Choose the region. Every call runs in the EU (eu) unless you ask for the US (us). Collections are per region, so ask for the same region each time you work with a collection.
The image links are placeholders: use a link to your own image. Prompts 2 to 5 build on each other and use the collection and the face that prompt 2 creates.
| # | Prompt | What happens |
|---|---|---|
| 1 | "Estimate the apparent age and gender of the face in https://example.com/photos/visitor.jpg." | verifeye_identify_face analyzes the face and returns the estimates. No face or image is stored. |
| 2 | "Create a VerifEye collection called front-desk-visitors, then onboard the face in https://example.com/photos/visitor-1042.jpg into it with the external key visitor-1042." | verifeye_create_collection creates the collection, and verifeye_onboard_face stores the face template with that key. Onboarding stores biometric data: see Biometric data and consent. |
| 3 | "Is the person in https://example.com/photos/today.jpg already in my front-desk-visitors collection?" | verifeye_identify_face with that collection answers Existing, with the faceId and the key, when the photo shows the person onboarded in prompt 2, and NotExisting for anyone else. Nothing is onboarded. |
| 4 | "Compare the face in https://example.com/photos/check-in.jpg with visitor-1042 in front-desk-visitors." | verifeye_get_face_by_key finds the faceId, and verifeye_compare_face returns the similarity and VerifEye's isMatch verdict. |
| 5 | "Delete visitor-1042's face from front-desk-visitors." | verifeye_get_face_by_key finds the face, and verifeye_delete_face destroys its template. This cannot be undone. |
Many clients ask you to approve a call before it runs, for example before a face is onboarded or deleted.
Every tool takes region (eu or us, eu by default), which selects where the image is processed and where a collection lives. Collections are per region: one created in eu is not visible from us.
| Tool | What it does | Stores or destroys data |
|---|---|---|
verifeye_identify_face | Analyzes the face(s) in an image, and identifies them against a collection if you name one | No |
verifeye_onboard_face | Onboards the face(s) in an image into a collection so the person is identified later | Stores a face template |
verifeye_compare_face | Compares the face(s) in an image against one onboarded face | No |
verifeye_delete_face | Deletes one onboarded face | Irreversible |
verifeye_list_collections | Lists the collections on the account, or checks whether one exists | No |
verifeye_create_collection | Creates an empty collection | No |
verifeye_set_collection_description | Replaces a collection's description | No |
verifeye_reset_collection | Deletes every face in a collection, keeping the collection | Irreversible |
verifeye_delete_collection | Deletes a collection and every face in it | Irreversible |
verifeye_get_face_by_key | Finds an onboarded face by your own identifier | No |
verifeye_set_face_key | Attaches your own identifier to an onboarded face | No |
verifeye_delete_face_key | Removes your identifier from an onboarded face | Loses the way of finding the face |
verifeye_get_upload_url | Hands back a short-lived form for uploading one image | No |
Parameters, results and error codes for each tool are in the documentation.
These tools process facial (biometric) data. You are responsible for obtaining valid, informed consent before a call runs, and for meeting the privacy and biometric-data regulations that apply to the people in your images (for example GDPR, BIPA and CCPA).
verifeye_onboard_face stores a face template that persists until it is deleted.verifeye_delete_face, verifeye_reset_collection and verifeye_delete_collection destroy face templates permanently.ai.realeyes/verifeye): https://registry.modelcontextprotocol.io/v0.1/servers/ai.realeyes%2Fverifeye/versions/latest