Facehunch MCP server

Facehunch MCP

Photo-search context with clear limits.

Facehunch helps readers understand photo-search methods, source pages and the limits of a visual result. Its guides distinguish finding copies of a photograph from comparing faces across different photographs. The workspace presents a fictional sample and consented API tests; the current FaceCheck test index does not produce reliable identity matches.

Website · MCP repository · Agent skill · npm package

What this connector does

This package connects a local stdio MCP client to the hosted Facehunch MCP server. Hosted tools run on Cloudflare; the local package bridges the connection and opens browser-based OAuth. You do not need to deploy a Worker or paste a product password into your assistant.

The MCP does not initiate new face searches, identify people, infer sensitive traits or research personal information. It only retrieves existing owned reports. Locked results remain hidden. An empty report list means the account has no saved reports, not that a photograph has no online matches. Test results are not identity verification.

Example workflow

1. Locate a report that already exists in the user’s account.
2. Read its status and access state; preserve dates and source URLs exactly as returned.
3. Summarize what the stored report contains without inferring identity or treating a similarity score as verification.

Things to ask your assistant

List my saved reports with their dates, statuses and links.

Open this existing report and summarize its available source links without identifying anyone.

Check whether this report is accessible. If it is locked, return its product link instead of guessing its contents.

Connect a remote MCP client

1. Open the client’s custom MCP or connector settings.
2. Enter https://mcp.facehunch.com/mcp as the remote server URL.
3. Complete Facehunch sign-in in your browser and review the permissions on the consent screen.
4. Return to the client and load the available tools.

Use a client that supports Streamable HTTP MCP and OAuth. Custom-connector availability depends on the client and your account. A public repository or npm release does not mean the integration has been approved for a client’s marketplace.

Claude Desktop and other stdio clients

Requires Node.js 22 or newer and an existing Facehunch account. Add this entry to your client’s MCP configuration:

{
  "mcpServers": {
    "facehunch": {
      "command": "npx",
      "args": [
        "-y",
        "facehunch-mcp"
      ]
    }
  }
}

You can also run npx -y facehunch-mcp from a terminal to start the bridge. It speaks MCP over stdio; it is not an interactive chat interface. For desktop clients that support MCPB extensions, download the .mcpb file from Facehunch releases.

Permissions and account access

Requested scopes: profile:read reports:read. Older profile-only connections need to reconnect and explicitly approve the additional permissions before content tools are available.

Only approve a connection you intended to start. If sign-in opens a new tab, finish it, return to the consent screen and refresh. Manage or revoke connected apps.

Shortened. The full README is on GitHub.