whowhy

io.whowhyPublished by whowhy.ioOfficial publisherv5.257.1Updated Nov 1, 2026

Double opt-in intros for hiring: whowhy finds the people, writes to them, you meet who says yes.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote whowhy server for hiring intros: it finds candidates, contacts them on your behalf, and you meet only those who opt in.

What you can do
  • The listing names no tools, so capabilities come from the short description only.
  • It is positioned around double opt-in introductions for hiring.
  • It finds the people to approach on your behalf.
  • It writes to those people, and you meet only the ones who say yes.
When to use it
When you are hiring and want warm, consent-based introductions rather than cold outreach, and you are comfortable letting the service contact candidates for you.
Requirements
A remote streamable HTTP endpoint at api.whowhy.io; OAuth authentication is required. No environment variables or headers are declared.
Before you install
The service sends messages to real people on your behalf, so review what it writes and to whom before enabling it. It requires OAuth sign-in to a third-party account, and candidate data is shared with that provider.

Installation

In SourceWeft

  1. Open whowhy 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.whowhy%2Fwhowhy/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": {
    "whowhy": {
      "type": "http",
      "url": "https://api.whowhy.io/functions/v1/mcp-server/directory"
    }
  }
}

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

2
  1. v5.257.1LatestNov 1, 2026
  2. v5.248.0Oct 22, 2026

Score

83% 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
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.