AyHire

com.ayhirePublished by ayhire.comOfficial publisherv1.0.0Updated Oct 24, 2026

Hire engineers by what they shipped: find, judge and shortlist developers from public GitHub work.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

AyHire is a remote MCP server that lets an assistant find, evaluate and shortlist engineers based on their public GitHub work.

What you can do
Search for developers using their public GitHub work as the basis for matching and discovery. Assess candidates by what they have shipped rather than by self-reported profiles. Build and manage shortlists of engineers for hiring decisions. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when a recruiter or hiring team wants an assistant to source and compare engineering candidates from public GitHub activity, and to keep a shortlist of promising people.
Requirements
A remote streamable HTTP endpoint at ayhire.com; no local package or runtime is needed. OAuth authentication is required, so the user must sign in or authorize the connection. No environment variables or headers are declared.
Before you install
The connection requires OAuth authorization, granting the server access tied to the user's account. Candidate judgments are derived from public GitHub data, which may be incomplete or misleading and should not be the sole basis for hiring decisions. The manifest lists no tools, so what data is read or written is not documented.

Installation

In SourceWeft

  1. Open AyHire 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/com.ayhire%2Fayhire/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": {
    "ayhire": {
      "type": "http",
      "url": "https://ayhire.com/mcp"
    }
  }
}

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.0.0LatestOct 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.