General Tools
queryquarry.com
This MCP server provides tools for searching, evaluating, contacting candidates, and tracking recruitment outcomes.
ENDPOINT 1
https://queryquarry.com/api/mcp
MCP server metadata
- Name
- queryquarry
- Version
- 1.0.0
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.
Known tools 11
get_candidateEvaluate one candidate in depth — full skills, summary, seniority, experience (titles + what they did) and education.
Inferred read-onlyget_contactCheck 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.
Potential side effectsreport_contact_outcomeOne-tap outcome report on an accepted contact: did it lead to a hire?
Inferred read-onlyget_new_candidatesGet resumes new or updated since a timestamp (your standing alert).
Inferred read-onlyget_corpus_statsGet aggregate stats about the talent corpus (counts, top skills/locations).
Inferred read-onlycheck_subscriptionCheck your subscription tier, status, rate limit, and usage this hour.
Inferred read-onlyget_docsGet the full QueryQuarry reference (how it works, all tools and filters, search tips, rate limits, privacy).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.queryquarry]
url = "https://queryquarry.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"queryquarry": {
"type": "http",
"url": "https://queryquarry.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: queryquarry
Remote MCP URL: https://queryquarry.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"queryquarry": {
"url": "https://queryquarry.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"queryquarry": {
"type": "http",
"url": "https://queryquarry.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "queryquarry",
"transport": "streamable-http",
"url": "https://queryquarry.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.