Skip to content
External endpointresponds

queryquarry

Double-blind talent marketplace: AIs search anonymous opted-in candidates; reveal on consent.

Endpoint URL
https://queryquarry.com/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
856 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.QueryQuarry/queryquarry

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
queryquarry
Version
1.0.0
Capability keys
tools
Tool names
search_candidates, get_candidate, request_contact, get_contact, report_contact_outcome, get_new_candidates, save_candidate, get_watchlist, get_corpus_stats, check_subscription, get_docs
Instructions excerpt

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

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 106ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 894ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 743ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 856ms