Facesign Mcp

ai.facesignPublished by facesign.aiOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

FaceSign MCP lets an AI assistant set an API key, inspect FaceSign verification sessions, launch a local session UI, and export a session as a Next.js app.

What you can do
Authenticate the session with a FaceSign API key, optionally overriding the API server URL for development use. List and retrieve FaceSign sessions, including status, transcripts, AI analysis, node reports and asynchronous analysis states. Launch a local web page in the browser to run a FaceSign session with supplied landing and recap HTML plus per-language UI strings. Export the current session configuration as a standalone, deployable Next.js application.
When to use it
Useful when building or testing FaceSign step-up verification flows from an AI coding tool, or when you need to review existing sessions and their analysis results.
Requirements
A remote MCP endpoint at mcp.facesign.ai. A FaceSign API key from the FaceSign dashboard, supplied through the set_api_key tool before any other tool is used. Browser access for launching the local session page.
Before you install
The API key is a secret and is passed to the server through a tool call; treat it as sensitive. The server can launch a local web page and export a deployable application, which writes files and code you should review before deploying. Session data, including transcripts and analysis, is retrieved from FaceSign.

Installation

In SourceWeft

  1. Open Facesign Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.facesign%2Ffacesign-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

5

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.

ParametersapiKeyrequiredserverUrl

get_session

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

ParameterssessionIdrequired

list_sessions

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

ParameterslimitcursorflowIdsearchsortBystatustoDatefromDatesortOrderclientReferenceId

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.

ParametersflowrequiredzonelangsavatarIdmetadatarecapHtmlrequireduiStringsrequireddefaultLanglandingHtmlrequiredprovidedDatacustomizationextractionSchema+3 more

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.

ParametersflowrequiredzonelangsappNameavatarIdmetadatarecapHtmlrequireduiStringsrequireddefaultLanglandingHtmlrequiredflowVariantsprovidedData+5 more

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.