DevMatch

DevMatch — evidence-based engineer hiring for mission-driven teams.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    DevMatch — evidence-based engineer hiring for mission-driven teams.

    Server tool list (3)

    Raw names from tools/list. Only developers need these.

    find_candidatesFind engineers who uniquely fit a role or project from open-source contributions and other public work, with evidence. Input: pass the richest context you have — (1) a full job description (most common), (2) a synthesized brief after reviewing a company's public repo (README + stack + role needs — preferred over a bare URL when you've evaluated the project), (3) a public github.com repo URL (server fetches README/topics; private repos → paste README as text), or (4) an informal role brief. Longer, more specific input produces a tighter mission fit. Optional `location` narrows to a city, country, or ISO country code. Returns up to limit candidates (default 20, max 20) with full inline profiles in structuredContent (view=candidates): login, name, bio, location, followers, reach (cross-platform audience percentile + reach), html_url, top_repos, signals, matched_projects, location_match, and contact (top_topics / top_domains / top_languages / top_subtopics are optional until software-topic backfill). Results never include bots, CI, or service accounts — they are filtered out automatically. Use the optional `exclude` array (GitHub logins or org names) to drop additional accounts. AGENT MODE: consume structuredContent only. HUMAN MODE: MCP App panel shows candidate cards; use server instructions for text-only hosts. Do not call get_profile for handles already in these results unless the user asks for deeper detail. Defense (SBIR), NRC filings, and mining QP consents are matched by lexical FTS over award titles, accessions, and consent letters — not abstract similarity. Publication, NTRS, repo, and TechPort roles still use description vectors. Do not claim a semantic abstract match for an NRC accession or a QP consent.
    get_profileFetch one contributor's profile card by GitHub login, ORCID iD (or orcid.org URL), or a find_candidates `id` (source:name such as ntrs:Ada Lovelace). Do not invent a GitHub handle for research or deep-tech people — pass their id. find_candidates already returns full inline profiles; use get_profile only for ids outside those results or when the user asks for deeper detail. Returns structuredContent (view=profile). Agents: consume structuredContent only. IMPORTANT — interpreting recent_activities: indexed GitHub activity in the current ingestion window (2025–2026), up to ~20 events per recent project. NOT a complete career history. Empty or older activity does not mean inactive.
    find_similar_projectsFind open-source projects similar to a seed GitHub repo, closest in description, topics, and README. Each result includes top contributors as leads — not a hiring shortlist. Returns structuredContent (view=similar_projects). Agents: consume structuredContent only. Use for landscape mapping or to discover anchor repos; follow with find_candidates for hiring matches.