mcpbeat Sign in

StarHunt MCP Server

answering

StarHunt is answering right now. Last checked 5 min ago.

Hiring developers? Find and source software engineers by what they build on GitHub.

Uptime history 58 days of history · worst day 90%
58 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
202 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check StarHunt every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add github-developer-sourcing --transport http https://app.getstarhunt.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.getstarhunt.com/mcp
~/.codex/config.toml
[mcp_servers.github-developer-sourcing]
url = "https://app.getstarhunt.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "github-developer-sourcing": {
      "url": "https://app.getstarhunt.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "github-developer-sourcing": {
      "type": "http",
      "url": "https://app.getstarhunt.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.getstarhunt.com/mcp streamable-http sign-in 227 ms 5 min ago

Alternatives to StarHunt

same job, measured the same way
StarHunt
by getstarhunt

Find engineers by what they build on GitHub. Search by technology, location and role.

answering
AyHire
by ayhire

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

answering
Githunt MCP
by githunt-agent

Search, rank, and analyze GitHub developers for tech recruiting via GitHunt's API.

48 installs/wk answering
Legwork
by kumarganduri

Lets your AI find open-source tools on GitHub and install them as sandboxed MCP tools.

924 installs/wk local only
WingFoil
by wingfoil

WingFoil — the repo-native intent layer for AI-native software engineering

148 installs/wk local only
Cloud Agent
by joepangallo

AI software engineer — writes code, opens PRs, reviews code, generates tests, and more.

13 installs/wk local only
opsen
by opsen

Engineering spend: GitHub seats, Copilot, Actions and coding agents, priced, with fixes

answering
Codebahn
by codebahn

Codebahn is the private GitHub alternative: fast Git and CI for developers and teams.

answering

StarHunt — questions

Answers built from our own checks of this server.

Why is there no tool list for StarHunt?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is StarHunt working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 202 ms. The bar chart above shows every period we have measured.
How do I connect StarHunt?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to StarHunt?
No API key is involved. StarHunt answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is StarHunt?
It answers our handshake in 202 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.