Build and test FaceSign step-up verification flows from your AI coding tool
Connect Remote server
claude mcp add --transport http facesign-mcp https://mcp.facesign.ai/mcp
{
"mcpServers": {
"facesign-mcp": {
"url": "https://mcp.facesign.ai/mcp"
}
}
}
{
"servers": {
"facesign-mcp": {
"type": "http",
"url": "https://mcp.facesign.ai/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.facesign.ai/mcp
Tools 5 found in our last check
set_api_keySet 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…
get_sessionRetrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.
list_sessionsList FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.
launch_session_uiREQUIRES 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…
export_appExport 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 H…
Details
| Endpoint | https://mcp.facesign.ai/mcp (Streamable HTTP) |
| First published | 19 Aug 2026 |
| Last updated | 19 Aug 2026 |
| Registry name | ai.facesign/facesign-mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
