ai.facesign/facesign-mcp · v0.1.0 · ai-and-media
ai.facesign/facesign-mcp is healthy: it completed an MCP handshake in 2007 ms and exposes 5 tools. It scores 58/100.
Build and test FaceSign step-up verification flows from your AI coding tool
Endpoint: https://mcp.facesign.ai/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| health | 18 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 5 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 5 / 10 |
Scoring v0.3, computed 2026-10-15T02:26:19.228Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T09:00:12.653Z | Healthy | 2007 |
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 `serverUrl` — intended for FaceSign developers pointing the SDK at |
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 finishes), and `uiStrings` (a per-language dictionary whose keys |
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 invented by you to match placeholders in the HTML). The exported ap |