Skip to content
FaceSign logo

FaceSign MCP server

Which servers in the official MCP registry are FaceSign's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to FaceSign

Whose server it is
  • Registry nameai.facesign/facesign-mcpverified in the MCP registry

The registry name sits under facesign.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Stateanswerschecked 2026-10-19
  • Tools5
  • Server calls itselffacesign
  • Server version3.3.0
  • Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 177 ms.

Measured dailydaily checks: 2, the first on 2026-10-19
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer212 ms
  • Space in an agent's context≈ 21,198 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Not saying whether it only reads or can destroy: 5 of 5

Worth a look

  • Tools that change data, on a server that answers without a sign-in: set_api_key

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-19
  • set_api_key

    Set your FaceSign API key for this session. This must be called before any other FaceSign tools. Get your API key from the FaceSign dashboard. The key starts with sk_live_... or sk_test_... Optionally override the API server URL via…

  • get_session

    Retrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.

  • list_sessions

    List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.

  • launch_session_ui

    REQUIRES set_api_key to be called first. Launch a local web page in the browser for a FaceSign session. You MUST supply `landingHtml` (the pre-session page shown before the iframe), `recapHtml` (the results page shown after the session…

  • export_app

    Export the current FaceSign session configuration as a standalone, deployable Next.js application. You MUST supply `landingHtml` (pre-session page), `recapHtml` (results page), and `uiStrings` (per-language dictionary whose keys are…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "facesign-mcp": {
      "type": "http",
      "url": "https://mcp.facesign.ai/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.