Facesign is a remote MCP server that gives an AI agent 5 tools, among them export_app, get_session, launch_session_ui. It answers at https://mcp.facesign.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Build and test FaceSign step-up verification flows from your AI coding tool
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 invente |
get_session | Retrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states. Inputs: sessionId |
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 fini |
list_sessions | List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor. Inputs: status, fromDate, toDate, search, sortBy, sortOrder |
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 `server Inputs: apiKey, serverUrl |
Every block below points at https://mcp.facesign.ai/mcp. Pick your client and copy.
claude mcp add --transport http facesign https://mcp.facesign.ai/mcp
{
"mcpServers": {
"facesign": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.facesign.ai/mcp"]
}
}
}{
"mcpServers": {
"facesign": {
"url": "https://mcp.facesign.ai/mcp"
}
}
}{
"servers": {
"facesign": {
"type": "http",
"url": "https://mcp.facesign.ai/mcp"
}
}
}{
"context_servers": {
"facesign": {
"url": "https://mcp.facesign.ai/mcp"
}
}
}{
"mcpServers": {
"facesign": {
"serverUrl": "https://mcp.facesign.ai/mcp"
}
}
}{
"mcpServers": {
"facesign": {
"url": "https://mcp.facesign.ai/mcp"
}
}
}name: Facesign
version: 0.0.1
schema: v1
mcpServers:
- name: Facesign
type: streamable-http
url: https://mcp.facesign.ai/mcp{
"mcpServers": {
"facesign": {
"httpUrl": "https://mcp.facesign.ai/mcp"
}
}
}{
"mcpServers": {
"facesign": {
"type": "http",
"url": "https://mcp.facesign.ai/mcp"
}
}
}{
"mcpServers": {
"facesign": {
"url": "https://mcp.facesign.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.facesign.ai%2Fmcp&type=streamable_http&id=facesign&name=Facesign
It answered our last check on 17 October 2026 in 550 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by facesign.ai and served from mcp.facesign.ai, the vendor's own domain: https://mcp.facesign.ai/mcp.
5, as returned by the server's own tools/list on 7 September 2026: export_app, get_session, launch_session_ui, list_sessions, set_api_key.
It answered our last check on 17 October 2026 in 550 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.facesign.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.facesign. Endpoint host: mcp.facesign.ai. ARD identifier: urn:air:ai.facesign:mcp:facesign-mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.