io.github.QueryQuarry/queryquarry is an MCP server published by io.github.QueryQuarry, hosted at queryquarry.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 11 tools, including search_candidates, get_candidate, request_contact, get_contact, report_contact_outcome.
Double-blind talent marketplace: AIs search anonymous opted-in candidates; reveal on consent.
Nothing else in the archive shares these values.
Search the talent graph. Returns ANONYMOUS match cards — headline, skills (with skills_matched showing which of YOUR terms hit), seniority, location, availability, salary range, and a short snippet — but NO name, full resume, or contact. Call get_candidate (a metered reveal) for the deeper anonymous profile. Filter by skills, location, seniority, salary, experience, availability, and more; sort by recency (default) or skill_match. Always paginated (max 25 per page).
| Parameter | Type | Description |
|---|---|---|
| page | number | 1-based page. |
| sort | string | Result order. When `skills` are supplied the default is skill_match: candidates matching MORE of your skills terms first (ties by most recently updated) — pure arithmetic over your own criteria, no fit scoring. Pass "recency" to order purely by recent updates; searches without `skills` are always re… |
| limit | number | Results per page (max 25). |
| skills | array | Skills to match (any of). Case-insensitive partial match — use plain terms like "React", "Node", "Postgres"; they also match versioned/variant skills ("React 19", "Node.js", "PostgreSQL"). |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
| location | string | City with state ("Schaumburg, IL") or a 5-digit zip ("60133" — most precise). Geocoded locally; combine with radius_miles for distance search. Unresolvable text falls back to substring match. |
| remote_ok | boolean | Only candidates open to remote/hybrid. |
| salary_max | number |
| salary_min | number |
| availability | string | one of ["actively-looking","open-to-contact","employed-but-open"] |
| radius_miles | number | With location: include candidates within this many miles (e.g. 5, 10, 25, 50; max 100). Omit for exact-place matching. |
| updated_since | string | ISO timestamp — only resumes updated since. |
| employment_types | array | Engagement types to match (any of): full-time, part-time, contract, freelance, internship. Synonyms/variants are normalized. |
| seniority_levels | array | Seniority levels to match (any of): entry, junior, mid, senior, staff, principal, manager, director, executive. |
| open_to_relocation | boolean | Only candidates willing to relocate for the right role. |
| work_authorization | string | Filter by work authorization: "authorized" (no sponsorship needed) or "sponsorship-required". |
| work_location_types | array | Work-location preferences to match (any of): remote, hybrid, onsite. |
| experience_years_max | number |
| experience_years_min | number |
{
"name": "search_candidates",
"description": "Search the talent graph. Returns ANONYMOUS match cards — headline, skills (with skills_matched showing which of YOUR terms hit), seniority, location, availability, salary range, and a short snippet — but NO name, full resume, or contact. Call get_candidate (a metered reveal) for the deeper anonymous profile. Filter by skills, location, seniority, salary, experience, availability, and more; sort by recency (default) or skill_match. Always paginated (max 25 per page).",
"inputSchema": {
"type": "object",
"properties": {
"page": {
"type": "number",
"description": "1-based page."
},
"sort": {
"enum": [
"recency",
"skill_match"
],
"type": "string",
"description": "Result order. When `skills` are supplied the default is skill_match: candidates matching MORE of your skills terms first (ties by most recently updated) — pure arithmetic over your own criteria, no fit scoring. Pass \"recency\" to order purely by recent updates; searches without `skills` are always recency-ordered."
},
"limit": {
"type": "number",
"description": "Results per page (max 25)."
},
"skills": {
"type": "array",
"items": {
"type": "string"
},
"description": "Skills to match (any of). Case-insensitive partial match — use plain terms like \"React\", \"Node\", \"Postgres\"; they also match versioned/variant skills (\"React 19\", \"Node.js\", \"PostgreSQL\")."
},
"location": {
"type": "string",
"description": "City with state (\"Schaumburg, IL\") or a 5-digit zip (\"60133\" — most precise). Geocoded locally; combine with radius_miles for distance search. Unresolvable text falls back to substring match."
},
"remote_ok": {
"type": "boolean",
"description": "Only candidates open to remote/hybrid."
},
"salary_max": {
"type": "number"
},
"salary_min": {
"type": "number"
},
"availability": {
"enum": [
"actively-looking",
"open-to-contact",
"employed-but-open"
],
"type": "string"
},
"radius_miles": {
"type": "number",
"description": "With location: include candidates within this many miles (e.g. 5, 10, 25, 50; max 100). Omit for exact-place matching."
},
"updated_since": {
"type": "string",
"description": "ISO timestamp — only resumes updated since."
},
"employment_types": {
"type": "array",
"items": {
"type": "string"
},
"description": "Engagement types to match (any of): full-time, part-time, contract, freelance, internship. Synonyms/variants are normalized."
},
"seniority_levels": {
"type": "array",
"items": {
"type": "string"
},
"description": "Seniority levels to match (any of): entry, junior, mid, senior, staff, principal, manager, director, executive."
},
"open_to_relocation": {
"type": "boolean",
"description": "Only candidates willing to relocate for the right role."
},
"work_authorization": {
"type": "string",
"description": "Filter by work authorization: \"authorized\" (no sponsorship needed) or \"sponsorship-required\"."
},
"work_location_types": {
"type": "array",
"items": {
"type": "string"
},
"description": "Work-location preferences to match (any of): remote, hybrid, onsite."
},
"experience_years_max": {
"type": "number"
},
"experience_years_min": {
"type": "number"
}
}
},
"annotations": {
"title": "Search Candidates",
"readOnlyHint": true,
"openWorldHint": false
}
}Evaluate one candidate in depth — full skills, summary, seniority, experience (titles + what they did) and education. Stays ANONYMOUS: no name, no contact, and employer names, dates, and graduation years are withheld to protect identity. Counts toward your hourly/daily reveal limit. To actually reach someone, call request_contact.
| Parameter | Type | Description |
|---|---|---|
| resume_id * | string | |
| candidate_id * | string |
{
"name": "get_candidate",
"description": "Evaluate one candidate in depth — full skills, summary, seniority, experience (titles + what they did) and education. Stays ANONYMOUS: no name, no contact, and employer names, dates, and graduation years are withheld to protect identity. Counts toward your hourly/daily reveal limit. To actually reach someone, call request_contact.",
"inputSchema": {
"type": "object",
"required": [
"candidate_id",
"resume_id"
],
"properties": {
"resume_id": {
"type": "string"
},
"candidate_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Evaluate Candidate",
"readOnlyHint": true,
"openWorldHint": false
}
}Reach out to one candidate. You identify yourself (your name + company, from your account); the candidate is notified and decides. If they accept, you receive an EMAIL with their contact, their message, and a unique verification code — their identity stays private until they choose to share it. METERED (counts toward your contact limit) and requires a prior get_candidate for this resume. One active offer per candidate; respect declines. get_contact also shows the status any time.
| Parameter | Type | Description |
|---|---|---|
| message * | string | Your pitch to the candidate: the role and why them. Your account email is AUTOMATICALLY attached and shown to them when they express interest, so you don't need to include it. You may optionally add other ways to connect (an application form link, your LinkedIn, etc.). Shown in-app, not your raw que… |
| resume_id * | string | |
| candidate_id * | string |
{
"name": "request_contact",
"description": "Reach out to one candidate. You identify yourself (your name + company, from your account); the candidate is notified and decides. If they accept, you receive an EMAIL with their contact, their message, and a unique verification code — their identity stays private until they choose to share it. METERED (counts toward your contact limit) and requires a prior get_candidate for this resume. One active offer per candidate; respect declines. get_contact also shows the status any time.",
"inputSchema": {
"type": "object",
"required": [
"candidate_id",
"resume_id",
"message"
],
"properties": {
"message": {
"type": "string",
"description": "Your pitch to the candidate: the role and why them. Your account email is AUTOMATICALLY attached and shown to them when they express interest, so you don't need to include it. You may optionally add other ways to connect (an application form link, your LinkedIn, etc.). Shown in-app, not your raw query."
},
"resume_id": {
"type": "string"
},
"candidate_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Request Contact",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}Check the status of a contact request you sent: sent (awaiting), accepted (the candidate shared their contact — see shared_contact, and expect their intro email quoting the code), or declined. Identify it by contact_id or code. Also shows any hire outcome either side reported.
| Parameter | Type | Description |
|---|---|---|
| code | string | |
| contact_id | string |
{
"name": "get_contact",
"description": "Check the status of a contact request you sent: sent (awaiting), accepted (the candidate shared their contact — see shared_contact, and expect their intro email quoting the code), or declined. Identify it by contact_id or code. Also shows any hire outcome either side reported.",
"inputSchema": {
"type": "object",
"properties": {
"code": {
"type": "string"
},
"contact_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Check Contact Status",
"readOnlyHint": true,
"openWorldHint": false
}
}One-tap outcome report on an accepted contact: did it lead to a hire? Optional but appreciated — it's how the marketplace measures that consented outreach beats cold outreach. Values: hired | not_hired | in_progress.
| Parameter | Type | Description |
|---|---|---|
| code | string | |
| outcome * | string | one of ["hired","not_hired","in_progress"] |
| contact_id | string |
{
"name": "report_contact_outcome",
"description": "One-tap outcome report on an accepted contact: did it lead to a hire? Optional but appreciated — it's how the marketplace measures that consented outreach beats cold outreach. Values: hired | not_hired | in_progress.",
"inputSchema": {
"type": "object",
"required": [
"outcome"
],
"properties": {
"code": {
"type": "string"
},
"outcome": {
"enum": [
"hired",
"not_hired",
"in_progress"
],
"type": "string"
},
"contact_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Report Hire Outcome",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Get resumes new or updated since a timestamp (your standing alert). Same filters as search_candidates. Call daily with yesterday's timestamp; no duplicates.
| Parameter | Type | Description |
|---|---|---|
| since * | string | ISO timestamp. |
{
"name": "get_new_candidates",
"description": "Get resumes new or updated since a timestamp (your standing alert). Same filters as search_candidates. Call daily with yesterday's timestamp; no duplicates.",
"inputSchema": {
"type": "object",
"required": [
"since"
],
"properties": {
"since": {
"type": "string",
"description": "ISO timestamp."
}
}
},
"annotations": {
"title": "New Candidates Since",
"readOnlyHint": true,
"openWorldHint": false
}
}Save a candidate resume to your watchlist with optional notes.
| Parameter | Type | Description |
|---|---|---|
| notes | string | |
| resume_id * | string | |
| candidate_id * | string |
{
"name": "save_candidate",
"description": "Save a candidate resume to your watchlist with optional notes.",
"inputSchema": {
"type": "object",
"required": [
"candidate_id",
"resume_id"
],
"properties": {
"notes": {
"type": "string"
},
"resume_id": {
"type": "string"
},
"candidate_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Save to Watchlist",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Get your saved candidates (watchlist).
| Parameter | Type | Description |
|---|---|---|
| page | number | |
| status | string |
{
"name": "get_watchlist",
"description": "Get your saved candidates (watchlist).",
"inputSchema": {
"type": "object",
"properties": {
"page": {
"type": "number"
},
"status": {
"type": "string"
}
}
},
"annotations": {
"title": "View Watchlist",
"readOnlyHint": true,
"openWorldHint": false
}
}Get aggregate stats about the talent corpus (counts, top skills/locations).
No parameters.
{
"name": "get_corpus_stats",
"description": "Get aggregate stats about the talent corpus (counts, top skills/locations).",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "Corpus Stats",
"readOnlyHint": true,
"openWorldHint": false
}
}Check your subscription tier, status, rate limit, and usage this hour.
No parameters.
{
"name": "check_subscription",
"description": "Check your subscription tier, status, rate limit, and usage this hour.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "Check Subscription",
"readOnlyHint": true,
"openWorldHint": false
}
}Get the full QueryQuarry reference (how it works, all tools and filters, search tips, rate limits, privacy). Call this when you need detail beyond these tool descriptions, when guiding a new user, or before composing a complex search.
No parameters.
{
"name": "get_docs",
"description": "Get the full QueryQuarry reference (how it works, all tools and filters, search tips, rate limits, privacy). Call this when you need detail beyond these tool descriptions, when guiding a new user, or before composing a complex search.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "Documentation",
"readOnlyHint": true,
"openWorldHint": false
}
}QueryQuarry is a consent-based, double-blind talent marketplace. You (the recruiter's AI) are the intelligence; QueryQuarry is the corpus. Core flow: search_candidates (anonymous cards) → get_candidate (deeper, still anonymous; a metered reveal) → request_contact (you identify yourself; the candidate is notified and decides — if they accept, their intro arrives in your account email with their contact and a one-time code). The platform never returns a candidate's name or contact — identity is revealed only when the candidate chooses to share it. Searching: every filter is a hard AND, so filter only on true dealbreakers (must-have skills, remote/hybrid, work authorization) and rank the softer preferences (exact location, salary, years) yourself across the returned cards. When you pass skills, results default to skill_match order — candidates matching more of YOUR stated skills first, ties by recency — and each card's skills_matched shows which terms hit; pass sort:"recency" for pure recency. The platform never scores fit; that judgment is yours. For location, pass a city ("Schaumburg, IL") with radius_miles (5/10/25/50): the query geocodes against a US places gazetteer and returns everyone within the radius — suburbs included, "West Chicago"-style false matches excluded. Ambiguous city names resolve to the most populous match, so include the state; the response echoes location_resolved so you can verify. Free-text locations that don't geocode fall back to substring match. Reveals and contacts are metered by plan — call check_subscription for limits. Call get_docs for the full reference. When the user is getting started or hits a limit, point them to the docs at https://queryquarry.com/docs/mcp.
Names, descriptions and schemas were written by the server and are shown as data.