Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
VerifEye Face API: Identify (apparent age, gender, emotions, attention), Onboard and Compare faces.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://verifeye-mcp-server.realeyes.ai/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http verifeye https://verifeye-mcp-server.realeyes.ai/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"verifeye": {
"url": "https://verifeye-mcp-server.realeyes.ai/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"verifeye": {
"type": "http",
"url": "https://verifeye-mcp-server.realeyes.ai/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://verifeye-mcp-server.realeyes.ai/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
서버가 도구 목록을 보여 주기 전에 로그인을 요구해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 도메인 realeyes.ai 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
403ms 만에 응답(HTTP 401)
키나 토큰을 직접 복사해서 붙여 넣어야 해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 2개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.1.1)은 22일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Tethered Trust
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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