Double-blind talent marketplace: AIs search anonymous opted-in candidates; reveal on consent.
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Check your subscription tier, status, rate limit, and usage this hour.
This tool takes no arguments.
Check your subscription tier, status, rate limit, and usage this hour.
No arguments.
{
"type": "object",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| resume_id* | string | |
| candidate_id* | string |
{
"type": "object",
"required": [
"candidate_id",
"resume_id"
],
"properties": {
"resume_id": {
"type": "string"
},
"candidate_id": {
"type": "string"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| code | string | |
| contact_id | string |
{
"type": "object",
"properties": {
"code": {
"type": "string"
},
"contact_id": {
"type": "string"
}
}
}Get aggregate stats about the talent corpus (counts, top skills/locations).
No arguments.
{
"type": "object",
"properties": {}
}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 arguments.
{
"type": "object",
"properties": {}
}Get resumes new or updated since a timestamp (your standing alert). Same filters as search_candidates. Call daily with yesterday's timestamp; no duplicates.
| Argument | Type | Description |
|---|---|---|
| since* | string | ISO timestamp. |
{
"type": "object",
"required": [
"since"
],
"properties": {
"since": {
"type": "string",
"description": "ISO timestamp."
}
}
}Get your saved candidates (watchlist).
| Argument | Type | Description |
|---|---|---|
| page | number | |
| status | string |
{
"type": "object",
"properties": {
"page": {
"type": "number"
},
"status": {
"type": "string"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| code | string | |
| outcome* | string | |
| contact_id | string |
{
"type": "object",
"required": [
"outcome"
],
"properties": {
"code": {
"type": "string"
},
"outcome": {
"enum": [
"hired",
"not_hired",
"in_progress"
],
"type": "string"
},
"contact_id": {
"type": "string"
}
}
}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.
| Argument | 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 query. |
| resume_id* | string | |
| candidate_id* | string |
{
"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"
}
}
}Save a candidate resume to your watchlist with optional notes.
| Argument | Type | Description |
|---|---|---|
| notes | string | |
| resume_id* | string | |
| candidate_id* | string |
{
"type": "object",
"required": [
"candidate_id",
"resume_id"
],
"properties": {
"notes": {
"type": "string"
},
"resume_id": {
"type": "string"
},
"candidate_id": {
"type": "string"
}
}
}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).
| Argument | 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 recency-ordered. |
| 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"). |
| 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 |
| 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 |
{
"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"
}
}
}