Documentation

VerifEye MCP Server Release Notes

Version History

Version 1.0

Release Date: 2026-09-10

Features

  • Initial Release: the VerifEye MCP server, exposing VerifEye analysis to MCP-capable assistants over OAuth 2.1, with no API key in the client. See MCP Server.
  • verifeye_identify_face: one tool for every facial attribute VerifEye reports — apparent age, apparent gender, momentary emotions and momentary attention — in a single call. Age and gender are included; emotions and attention are an add-on that surcharges the faces the call is already charged for, at the rate in your plan, rather than adding a second charge. Requesting either applies it; requesting both does not apply it twice.
  • Emotions and attention: six emotion signals and three attention signals. Each signal is a momentary, single-frame observation, never a score: it comes back as observed, as determined not present, or as undetermined. Where the analysis has nothing to report for a face, the object is left out entirely rather than returned with every signal undetermined. See Absent versus undetermined.
  • The image is a public URL: pass imageUrl and VerifEye fetches the image itself, so nothing in the conversation has to carry image bytes. maxFaces accepts 1 to 4; the higher counts are available on the VerifEye Face API directly.
  • Or upload the image: verifeye_get_upload_url hands back a short-lived, single-use upload form for a client that has an image but nowhere public to put it, and the analysis then takes the returned uploadId instead of imageUrl. The image is stored in the region you ask for and deleted as soon as the first analysis returns. It needs a client that can make an outbound HTTPS request of its own — an assistant whose tools run in a sandbox with no egress cannot upload, and a public URL works everywhere.
  • Data residency per call: one global endpoint, and region (eu/us) chooses where each image is processed. Your account must be authorized in the region you ask for.
  • Connecting a client: a client either uses a pre-registered client ID or publishes a client ID metadata document and sends its URL — the tab for your client says which, and gives the exact value where there is one. Claude, Claude Code, Cursor and the Gemini CLI are covered, and so are ChatGPT, VS Code and Codex, which identify themselves by metadata document and need no client ID entered. See Connecting a client.
  • Consent screen: it shows what VerifEye knows about the application asking for access. One VerifEye recognises is named, with the logo it publishes; one that identified itself with a metadata document from an address VerifEye does not recognise is shown by that address alone, with no name or logo. Either way the screen says where the authorization will be delivered. Approve only a sign-in you have just started yourself.
  • Agent discovery: an agent card, an MCP server card and four published skill documents — estimate-age, detect-gender, detect-emotions and detect-attention — under /.well-known/, so an agent can discover what the server does without reading this page. Each skill's description names the image source, the face limit and the data-residency choice. The agent card and the MCP server card are at version 1.0.0.

For the latest updates, visit the VerifEye Developer Console