Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Nothing to run from here
Facesign is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Build and test FaceSign step-up verification flows from your AI coding tool
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http facesign-mcp https://mcp.facesign.ai/mcp
# 2 — ask your agent for something these tools do
# set_api_key, get_session, list_sessions and 2 more
Facesign costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FAAll 1 server
facesign1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http facesign-mcp https://mcp.facesign.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| apiKey | string | yes | Your FaceSign API key (sk_live_... or sk_test_...) |
| serverUrl | string | no | 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. |
Retrieve detailed information about a FaceSign session including status, transcript, AI analysis, node reports, video AI analysis, and asynchronous analysis lifecycle states.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | The session ID to retrieve |
List FaceSign sessions with optional filtering by status, date range, and search term. Supports pagination via cursor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | no | Filter by session status | |
| fromDate | number | no | Start of date range (Unix timestamp in ms) |
| toDate | number | no | End of date range (Unix timestamp in ms) |
| search | string | no | Search term to filter sessions |
| sortBy | string | no | Field to sort by |
| sortOrder | string | no | Sort direction |
| limit | number | no | Max sessions to return (1-100, default 10) |
| cursor | string | no | Pagination cursor from a previous response |
| clientReferenceId | string | no | Filter by client reference ID |
| flowId | string | no | Filter sessions by flow ID |
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 —
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow | array | yes | Array of nodes forming the session's directed graph |
| avatarId | string | no | Avatar ID from the facesign://catalog resource. |
| langs | array | no | 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 t |
| defaultLang | string | no | 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- |
| zone | string | no | Data processing zone |
| metadata | object | no | Arbitrary metadata to attach |
| clientReferenceId | string | no | Your own reference ID for this session |
| providedData | object | no | Pre-known user data |
| videoAIAnalysisEnabled | boolean | no | Enable video AI fraud analysis |
| extractionSchema | array | no | 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]: |
| customization | object | no | UI customization |
| 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 |
| 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_SESS |
| 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. Mus |
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 de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow | array | yes | Array of nodes forming the session's directed graph |
| flowVariants | object | no | 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. |
| avatarId | string | no | Avatar ID from the facesign://catalog resource. |
| langs | array | no | 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 language |
| defaultLang | string | no | 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 is |
| zone | string | no | Data processing zone |
| metadata | object | no | Arbitrary metadata to attach |
| clientReferenceId | string | no | Your own reference ID for this session |
| providedData | object | no | Pre-known user data |
| videoAIAnalysisEnabled | boolean | no | Enable video AI fraud analysis |
| extractionSchema | array | no | 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]: |
| customization | object | no | UI customization |
| 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 |
| 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_SESS |
| 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 la |
| appName | string | no | Name for the generated app (used in package.json, defaults to 'facesign-app') |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Facesign or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Facesign can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.