ai.facesign/facesign-mcp

REMOTE · MCP.FACESIGN.AI · SCANNED AUG 20

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

Available components

62 62 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability71

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 12722 tokens (~978/item across 13 items; 5 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.facesign.ai

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http ai-facesign-facesign-mcp https://mcp.facesign.ai/mcp

# ~/.codex/config.toml

[mcp_servers.ai-facesign-facesign-mcp]
url = "https://mcp.facesign.ai/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-facesign-facesign-mcp": {
      "type": "remote",
      "url": "https://mcp.facesign.ai/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add ai-facesign-facesign-mcp --url https://mcp.facesign.ai/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  ai-facesign-facesign-mcp:
    url: "https://mcp.facesign.ai/mcp"

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

20 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
19 Aug 26 62

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Aug 2026 · Probed https://mcp.facesign.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.facesign.ai	CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB	18 Sept 2025	18 Oct 2026	RSA 2048	SHA256-RSA	9a64953e937479b92b753cc8cf3a2106
SANs: *.facesign.ai, facesign.ai
CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA)	CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB	22 Mar 2021	21 Mar 2036	RSA 3072	SHA384-RSA	397a66cc2756362e0daa87ca6eabe3b1

DNSSEC insecure

Validation of mcp.facesign.ai. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
ai.	present	3799	8	Verified
facesign.ai.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.facesign.ai/mcp	Verified	200
http (plaintext)	http://mcp.facesign.ai/mcp	HTTPS enforced

MCP tools · 5 exposed · ~10,601 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

export_app ~5,064

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.

Input Output Examples

Name	Type	Req	Description
appName	string	–	Name for the generated app (used in package.json, defaults to 'facesign-app')
avatarId	string	–	Avatar ID from the facesign://catalog resource.
clientReferenceId	string	–	Your own reference ID for this session
customization	object	–	UI customization
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 one of the codes in `langs` (if `langs` i…
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.report.extractedData` as `{ [fieldName]:…
flow	array	yes	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 sends a graph.
landingHtml	string	yes	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 {{KEY}} placeholders (interpolated at inject…
langs	array	–	Optional whitelist of BCP-47 language codes (from facesign://catalog) the exported session may use. DEFAULT BEHAVIOUR (recommended): OMIT this parameter entirely — the app then supports every languag…
metadata	object	–	Arbitrary metadata to attach
providedData	object	–	Pre-known user data
recapHtml	string	yes	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')). Contract: reads window.__FACESIGN_SES…
uiStrings	object	yes	REQUIRED. Per-language UI string dictionary: { langId: { key: translatedString } }. You invent the keys to match {{KEY}} / window.t('KEY') in landingHtml and recapHtml. Must contain `en` plus every l…
videoAIAnalysisEnabled	boolean	–	Enable video AI fraud analysis
zone	string	–	Data processing zone

No output schema declared.

No examples provided.

get_session ~50

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

Input Output Examples

Name	Type	Req	Description
sessionId	string	yes	The session ID to retrieve

No output schema declared.

No examples provided.

launch_session_ui ~5,170

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.

Input Output Examples

Name	Type	Req	Description
avatarId	string	–	Avatar ID from the facesign://catalog resource.
clientReferenceId	string	–	Your own reference ID for this session
customization	object	–	UI customization
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 falls back to 'en' internally only as a last…
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.report.extractedData` as `{ [fieldName]:…
flow	array	yes	Array of nodes forming the session's directed graph
landingHtml	string	yes	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 {{KEY}} placeholders (interpolated at inject…
langs	array	–	Optional whitelist of BCP-47 language codes (from facesign://catalog) the session may use. DEFAULT BEHAVIOUR (recommended): OMIT this parameter entirely — the session then supports every language in…
metadata	object	–	Arbitrary metadata to attach
providedData	object	–	Pre-known user data
recapHtml	string	yes	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')). Contract: reads window.__FACESIGN_SES…
uiStrings	object	yes	REQUIRED. Per-language UI string dictionary: { langId: { key: translatedString } }. You invent the keys to match the {{KEY}} placeholders / window.t('KEY') calls in your landingHtml and recapHtml. Mu…
videoAIAnalysisEnabled	boolean	–	Enable video AI fraud analysis
zone	string	–	Data processing zone

No output schema declared.

No examples provided.

list_sessions ~153

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

Input Output Examples

Name	Type	Req	Description
clientReferenceId	string	–	Filter by client reference ID
cursor	string	–	Pagination cursor from a previous response
fromDate	number	–	Start of date range (Unix timestamp in ms)
limit	number	–	Max sessions to return (1-100, default 10)
search	string	–	Search term to filter sessions
sortBy	string	–	Field to sort by
sortOrder	string	–	Sort direction
status	–	–	Filter by session status
toDate	number	–	End of date range (Unix timestamp in ms)

No output schema declared.

No examples provided.

set_api_key ~164

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.

Input Output Examples

Name	Type	Req	Description
apiKey	string	yes	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 the production API.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

19 Aug 20 Aug