Build and test FaceSign step-up verification flows from your AI coding tool
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.facesign.ai/mcp5 tools · 665msset_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 pointing the SDK at…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…
| Parameter | Type | Description |
|---|---|---|
| apiKey* | string | Your FaceSign API key (sk_live_... or sk_test_...) |
| serverUrl | string | Optional FaceSign API server URL override. Only set this if the user explicitly asks to target a non-default server (e.g. a dev backend). Omit otherwise to use… |
get_sessionRetrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.Retrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.
| Parameter | Type | Description |
|---|---|---|
| sessionId* | string | The session ID to retrieve |
list_sessionsList FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.
| Parameter | Type | Description |
|---|---|---|
| status | — | Filter by session status |
| fromDate | number | Start of date range (Unix timestamp in ms) |
| toDate | number | End of date range (Unix timestamp in ms) |
| search | string | Search term to filter sessions |
| sortBy | string | Field to sort by |
| sortOrder | string | Sort direction |
| limit | number | Max sessions to return (1-100, default 10) |
| cursor | string | Pagination cursor from a previous response |
| clientReferenceId | string | Filter by client reference ID |
| flowId | string | Filter sessions by flow ID |
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 dictionary whose key…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 key…
| Parameter | Type | Description |
|---|---|---|
| flow* | array | Array of nodes forming the session's directed graph |
| avatarId | string | Avatar ID from the facesign://catalog resource. |
| langs | array | Optional whitelist of BCP-47 language codes (from facesign://catalog) the session may use. DEFAULT BEHAVIOUR (recommended): OMIT this parameter entirely — the… |
| defaultLang | string | Optional fallback BCP-47 language code used when the end-user's browser language is not in `langs`. DEFAULT BEHAVIOUR: OMIT this parameter. The MCP server fall… |
| zone | string | Data processing zone |
| metadata | object | Arbitrary metadata to attach |
| clientReferenceId | string | Your own reference ID for this session |
| providedData | object | Pre-known user data |
| videoAIAnalysisEnabled | boolean | Enable video AI fraud analysis |
| extractionSchema | array | Optional schema describing fields the FaceSign backend should extract from the session transcript using an LLM. Results are populated post-session at `session.… |
| customization | object | UI customization |
| landingHtml* | string | REQUIRED. Raw HTML/JS for the pre-session landing page. NO CDATA, NO markdown fences. Every visible string MUST come from `uiStrings` — reference them via {{KE… |
| recapHtml* | string | REQUIRED. Raw HTML/JS for the results/recap page. NO CDATA, NO markdown fences. Every visible string MUST come from `uiStrings` (via {{KEY}} or window.t('KEY')… |
| uiStrings* | object | REQUIRED. Per-language UI string dictionary: { langId: { key: translatedString } }. You invent the keys to match the {{KEY}} placeholders / window.t('KEY') cal… |
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 HTML). The exported a…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 a…
| Parameter | Type | Description |
|---|---|---|
| flow* | array | Array of nodes forming the session's directed graph |
| flowVariants | object | Optional additional flows declared at export time. The landing page selects one by calling window.__startSession({ flowId: 'variant-id' }); the browser never s… |
| avatarId | string | Avatar ID from the facesign://catalog resource. |
| langs | array | Optional whitelist of BCP-47 language codes (from facesign://catalog) the exported session may use. DEFAULT BEHAVIOUR (recommended): OMIT this parameter entire… |
| defaultLang | string | Optional fallback BCP-47 language code used when the end-user's browser language is not in `langs`. DEFAULT BEHAVIOUR: OMIT this parameter. When set, must be o… |
| zone | string | Data processing zone |
| metadata | object | Arbitrary metadata to attach |
| clientReferenceId | string | Your own reference ID for this session |
| providedData | object | Pre-known user data |
| videoAIAnalysisEnabled | boolean | Enable video AI fraud analysis |
| extractionSchema | array | Optional schema describing fields the FaceSign backend should extract from the session transcript using an LLM. Results are populated post-session at `session.… |
| customization | object | UI customization |
| landingHtml* | string | REQUIRED. Raw HTML/JS for the pre-session landing page. NO CDATA, NO markdown fences. Every visible string MUST come from `uiStrings` — reference them via {{KE… |
| recapHtml* | string | REQUIRED. Raw HTML/JS for the results/recap page. NO CDATA, NO markdown fences. Every visible string MUST come from `uiStrings` (via {{KEY}} or window.t('KEY')… |
| uiStrings* | object | REQUIRED. Per-language UI string dictionary: { langId: { key: translatedString } }. You invent the keys to match {{KEY}} / window.t('KEY') in landingHtml and r… |
| appName | string | Name for the generated app (used in package.json, defaults to 'facesign-app') |
5 of 5 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Build and test FaceSign step-up verification flows from your AI coding tool
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.