ai.facesign/facesign-mcp
REMOTE · MCP.FACESIGN.AI · SCANNED OCT 4
Build and test FaceSign step-up verification flows from your AI coding tool
Available components
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 → Why this is hard to 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 12735 tokens (~979/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety50
- Injection-marker check failed: the description of parameter "recapHtml" on tool "launch_session_ui" contains hidden, non-rendering content, an HTML comment, at byte 4456 of that field, plus 1 further marker(s) of the same kind. See how to fix → Fail
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ai.facesign/facesign-mcp server?
ai.facesign/facesign-mcp is a hosted endpoint at https://mcp.facesign.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.facesign.ai
claude mcp add --transport http ai-facesign-facesign-mcp 'https://mcp.facesign.ai/mcp'
{
"mcpServers": {
"ai-facesign-facesign-mcp": {
"url": "https://mcp.facesign.ai/mcp"
}
}
} {
"servers": {
"ai-facesign-facesign-mcp": {
"type": "http",
"url": "https://mcp.facesign.ai/mcp"
}
}
} [mcp_servers.ai-facesign-facesign-mcp] url = "https://mcp.facesign.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-facesign-facesign-mcp": {
"type": "remote",
"url": "https://mcp.facesign.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-facesign-facesign-mcp --url 'https://mcp.facesign.ai/mcp' --transport streamable-http
mcp_servers:
ai-facesign-facesign-mcp:
url: "https://mcp.facesign.ai/mcp" {
"McpServers": {
"ai-facesign-facesign-mcp": {
"Transport": "http",
"Url": "https://mcp.facesign.ai/mcp"
}
}
} assistant mcp add ai-facesign-facesign-mcp -t streamable-http -u 'https://mcp.facesign.ai/mcp'
{
"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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 8 Oct 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| 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.
| 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.
| 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 ~166
List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| clientReferenceId | string | – | Filter by client reference ID |
| cursor | string | – | Pagination cursor from a previous response |
| flowId | string | – | Filter sessions by flow ID |
| 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.
| 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.
What is the ai.facesign/facesign-mcp server?
ai.facesign/facesign-mcp is listed in the public MCP registry as ai.facesign/facesign-mcp. Build and test FaceSign step-up verification flows from your AI coding tool. This page covers its hosted endpoint (https://mcp.facesign.ai/mcp).
Is the ai.facesign/facesign-mcp server safe to use?
ai.facesign/facesign-mcp scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.facesign/facesign-mcp server expose?
ai.facesign/facesign-mcp exposes 5 tools: set_api_key, get_session, list_sessions, launch_session_ui, export_app. Their descriptions and schemas cost roughly 10,614 tokens of context every time the server is loaded.
Does the ai.facesign/facesign-mcp server require authentication?
No. We connected to ai.facesign/facesign-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.facesign/facesign-mcp server still maintained?
ai.facesign/facesign-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.