mcpbeat Sign in

Facesign MCP Server

answering

Facesign MCP is answering right now. Last checked 8 min ago. It exposes 5 tools.

Build and test FaceSign step-up verification flows from your AI coding tool

Uptime history 30 days of history
30 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
593 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 August 2026. No other catalogue keeps this.

24 Aug 3 tools changed the parameters they ask for export_app, launch_session_ui, list_sessions
24 Aug a tool changed version
20 Aug 2 tools changed the parameters they ask for export_app, launch_session_ui
20 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check Facesign MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add facesign-mcp --transport http https://mcp.facesign.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "facesign-mcp": {
      "url": "https://mcp.facesign.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.facesign-mcp]
url = "https://mcp.facesign.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "facesign-mcp": {
      "url": "https://mcp.facesign.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "facesign-mcp": {
      "url": "https://mcp.facesign.ai/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

api
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 a non-production backend (e.g. a dev server). Leave unset to use the default production API.
export
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 app ships NO default chrome — every visible string comes from you. Run with `npm install && npm run dev` or deploy to Vercel after setting FACESIGN_API_KEY.
launch
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 are invented by you to match placeholders in the HTML). The MCP server provides NO default chrome — every visible string comes from you. Each page load / refresh creates a fresh session.
session
get_session
Retrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.
sessions
list_sessions
List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.

Endpoints

URLTransportStateLatencyChecked
https://mcp.facesign.ai/mcp streamable-http answering 555 ms 8 min ago

Alternatives to Facesign MCP

same job, measured the same way
C
Overlayqa
by overlayqa

Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.

94 installs/wk local only
Splera
by sohaibt

A/B testing for vibe coders: create, track, and ship experiments from your AI coding agent.

20 installs/wk local only
Dreamlit
by dreamlit

Create, test, publish, and manage Dreamlit notification workflows from AI clients.

11 tools answering
BetaDrop
by betadrop-app

Publish iOS and Android builds to testers and manage share links from an AI coding agent.

421 installs/wk local only
Curate-Ipsum
by egoughnour

Code synthesis through belief revision, mutation testing, and verification

166 installs/wk local only
Human For AI
by humanforai

Hire a real human for real-world verification, product testing, AI output review, and errands.

81 installs/wk 6 tools answering
DVERA CT verification tools
by suresofttechnologies

DVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage.

local only
Simple MCP Server
by ormastes

Simple Language MCP server — code intelligence, debugging, build, test, and VCS tools

58 installs/wk local only

Facesign MCP — questions

Answers built from our own checks of this server.

What can Facesign MCP do?
It exposes 5 tools, read directly from the server on our last check. Among them: export_app, get_session, launch_session_ui, list_sessions, set_api_key. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Facesign MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 593 ms. The bar chart above shows every period we have measured.
How do I connect Facesign MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Facesign MCP need an API key?
No. Facesign MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Facesign MCP?
It answers our handshake in 593 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.