facesign-mcp server
ai.facesign/facesign-mcpfacesign.aistreamable-httpv0.1.0Scanned
Build and test FaceSign step-up verification flows from your AI coding tool
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- 6 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the facesign-mcp server can do
The facesign-mcp server is published by facesign.ai, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: set_api_key, launch_session_ui and export_app), but cannot delete data. 2 tools only read.
2 tools can send data out of your system (launch_session_ui and export_app).
The fixed checks matched 6 findings (base64-blob). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
export_appExport the current FaceSign session configuration as a standalone, deployable Next.js application.Can send data out3 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.providedData.phone): what the tool writes goes there.
Findings
- Warn
The input schema at properties.flow.items.anyOf[5].properties.outcomes.items.$ref contains a 56-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[5].properties.outcomes.items.$ref: "#/properties/flow/items/anyOf/2/properties/outcomes/items"
- Warn
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref contains a 68-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/source"
- Warn
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref contains a 77-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/provid..."
Description, as the server wrote it 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_session_uiREQUIRES set_api_key to be called first.Can send data out3 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.providedData.phone): what the tool writes goes there.
Findings
- Warn
The input schema at properties.flow.items.anyOf[5].properties.outcomes.items.$ref contains a 56-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[5].properties.outcomes.items.$ref: "#/properties/flow/items/anyOf/2/properties/outcomes/items"
- Warn
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref contains a 68-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/source"
- Warn
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref contains a 77-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/provid..."
Description, as the server wrote it 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.
set_api_keySet your FaceSign API key for this session.No findings
Why it is in this group
- The name "set_api_key" says "set": a word for a change.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
get_sessionRetrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.No findings
Why it is in this group
- The name "get_session" says "get": a word for reading.
Description, as the server wrote it Retrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.
list_sessionsList FaceSign sessions with optional filtering by status, date range, and search term.No findings
Why it is in this group
- The name "list_sessions" says "list": a word for reading.
Description, as the server wrote it List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.facesign.ai/mcp: tools/list returned 5 tools to an anonymous client, including set_api_key (write), launch_session_ui (write), export_app (write)
Findings
Matches of fixed checks, with the text they matched.
The input schema at properties.flow.items.anyOf[5].properties.outcomes.items.$ref contains a 56-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[5].properties.outcomes.items.$ref: "#/properties/flow/items/anyOf/2/properties/outcomes/items"
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref contains a 68-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/source"
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref contains a 77-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/provid..."
- Warnexport_app
The input schema at properties.flow.items.anyOf[5].properties.outcomes.items.$ref contains a 56-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[5].properties.outcomes.items.$ref: "#/properties/flow/items/anyOf/2/properties/outcomes/items"
- Warnexport_app
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref contains a 68-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.source.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/source"
- Warnexport_app
The input schema at properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref contains a 77-character base64 string.
What this check looks forMatched text
inputSchema.properties.flow.items.anyOf[12].properties.sourceB.properties.providedDataKey.$ref: "#/properties/flow/items/anyOf/12/properties/sourceA/properties/provid..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http facesign https://mcp.facesign.ai/mcpclaude mcp add --transport http facesign https://mcp.facesign.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__facesign__get_session",
"mcp__facesign__list_sessions"
],
"ask": [
"mcp__facesign__set_api_key",
"mcp__facesign__launch_session_ui",
"mcp__facesign__export_app"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as facesign. Review it before you use it.
Capability tags behind 2 rules
- mcp__facesign__launch_session_ui outbound
- mcp__facesign__export_app outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.facesign/facesign-mcp/verify?hash=8e530e036169b7bbc9b7ea50db5d14f41878f54fbbb0750cc650b4742b0a4bb2" | jq -e '.changed == false'Pinned hash 8e530e036169, from Nov 11, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.facesign/facesign-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.facesign/facesign-mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:41 UTC.
facesign-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the facesign-mcp server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the facesign-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the facesign-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the facesign-mcp server have?
- 5 tools: 3 write, 2 read. set_api_key, launch_session_ui, export_app, get_session and list_sessions.
Does the facesign-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the facesign-mcp server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): launch_session_ui and export_app.
Has the facesign-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.