Facehunch

io.github.facehunchPublished by GitHub account facehunchv1.2.1Updated Oct 24, 2026

Read-only MCP connector for Facehunch saved reports, access status and available source links.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Read-only connector that lets an assistant list and read the signed-in user's saved Facehunch photo-search reports, their status and stored source links.

What you can do
Read the signed-in account's profile context and access status via get_profile. List reports already owned by the account, with status and access metadata, via list_reports. Retrieve an owned report's metadata and available stored source links via get_report, while locked results stay hidden. Summarize what a stored report contains without inferring identity or treating a similarity score as verification.
When to use it
Useful when you already have saved Facehunch reports and want an assistant to find, open and summarize them, or to check whether a report is accessible before relying on its contents. Not intended for starting new searches or identifying people.
Requirements
A remote endpoint supporting Streamable HTTP MCP and OAuth, or the npm package facehunch-mcp run locally with Node.js 22 or newer. An existing Facehunch account and browser sign-in with the profile:read and reports:read scopes.
Before you install
Sign-in grants read access to your profile and saved reports; tokens stored locally by the OAuth bridge are credentials, so only approve connections you started and revoke unused ones. The connector is read-only and does not start new searches, but report contents and source links may be sensitive; empty results do not mean a photo has no online matches, and test results are not identity verification.

Installation

In SourceWeft

  1. Open Facehunch in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.facehunch%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "facehunch": {
      "type": "http",
      "url": "https://mcp.facehunch.com/mcp"
    }
  }
}

README

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.

ToolWhat it does
get_profileRead the signed-in account context.
list_reportsList reports already owned by the account, with status and access metadata.
get_reportRetrieve an owned report’s metadata and available stored source links while respecting locked results.

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:

json
{  "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.

The package uses pinned mcp-remote for OAuth, PKCE and local token storage. Tokens on your computer are credentials. The connector uses the fixed endpoint above and rejects command-line endpoint overrides. Product passwords and underlying provider credentials are not requested by this package.

Troubleshooting

  • No tools or insufficient permissions: reconnect through browser consent and check the selected account.
  • An empty list: confirm that the account owns the expected items. Empty results are different from a failed request.
  • A link asks you to sign in: open it with the owning product account; a private product link is not a public share link.
  • The browser blocks authorization: inspect the browser’s displayed error and restart an expired request from the client. Never send cookies or tokens in an issue.

Add the companion skill

The Facehunch agent skill explains how to select the right records, interpret results and respect the workflow’s limits:

sh
npx skills add facehunch/agent-skill

Learn more about Facehunch

Development and support

sh
npm cinpm testnpm run bundle

Report a connector issue with your client, Node.js version and a redacted error. Keep package.json, manifest.json, server/config.json, server.json and the lockfile version aligned for releases. GitHub Actions publishes versioned npm packages and MCPB assets. See LICENSE for the MIT license.

Source: README.md at commit 6452086

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.1LatestSep 22, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts