Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,556Letters: 14Defects: 1,331counted just now
teppi

Server definition

Hash
sha256:f39adf9288ed11a0fd08f907b2ded01b4c32a2d007b9cd276e71e9ac8b204cd7
What it is
What a remote MCP server returned when asked what it offers: 11 tools

The blob, as servednamed by its sha256

{ "instructions": "QueryQuarry is a consent-based, double-blind talent marketplace. You (the recruiter's AI) are the intelligence; QueryQuarry is the corpus.\n\nCore 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.\n\nSearching: 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.\n\nReveals 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.", "tools": [ { "description": "Check your subscription tier, status, rate limit, and usage this hour.", "inputSchema": { "properties": {}, "type": "object" }, "name": "check_subscription", "outputSchema": null }, { "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": { "properties": { "candidate_id": { "type": "string" }, "resume_id": { "type": "string" } }, "required": [ "candidate_id", "resume_id" ], "type": "object" }, "name": "get_candidate", "outputSchema": null }, { "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": { "properties": { "code": { "type": "string" }, "contact_id": { "type": "string" } }, "type": "object" }, "name": "get_contact", "outputSchema": null }, { "description": "Get aggregate stats about the talent corpus (counts, top skills/locations).", "inputSchema": { "properties": {}, "type": "object" }, "name": "get_corpus_stats", "outputSchema": null }, { "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": { "properties": {}, "type": "object" }, "name": "get_docs", "outputSchema": null }, { "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": { "properties": { "since": { "description": "ISO timestamp.", "type": "string" } }, "required": [ "since" ], "type": "object" }, "name": "get_new_candidates", "outputSchema": null }, { "description": "Get your saved candidates (watchlist).", "inputSchema": { "properties": { "page": { "type": "number" }, "status": { "type": "string" } }, "type": "object" }, "name": "get_watchlist", "outputSchema": null }, { "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": { "properties": { "code": { "type": "string" }, "contact_id": { "type": "string" }, "outcome": { "enum": [ "hired", "not_hired", "in_progress" ], "type": "string" } }, "required": [ "outcome" ], "type": "object" }, "name": "report_contact_outcome", "outputSchema": null }, { "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": { "properties": { "candidate_id": { "type": "string" }, "message": { "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.", "type": "string" }, "resume_id": { "type": "string" } }, "required": [ "candidate_id", "resume_id", "message" ], "type": "object" }, "name": "request_contact", "outputSchema": null }, { "description": "Save a candidate resume to your watchlist with optional notes.", "inputSchema": { "properties": { "candidate_id": { "type": "string" }, "notes": { "type": "string" }, "resume_id": { "type": "string" } }, "required": [ "candidate_id", "resume_id" ], "type": "object" }, "name": "save_candidate", "outputSchema": null }, { "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": { "properties": { "availability": { "enum": [ "actively-looking", "open-to-contact", "employed-but-open" ], "type": "string" }, "employment_types": { "description": "Engagement types to match (any of): full-time, part-time, contract, freelance, internship. Synonyms/variants are normalized.", "items": { "type": "string" }, "type": "array" }, "experience_years_max": { "type": "number" }, "experience_years_min": { "type": "number" }, "limit": { "description": "Results per page (max 25).", "type": "number" }, "location": { "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.", "type": "string" }, "open_to_relocation": { "description": "Only candidates willing to relocate for the right role.", "type": "boolean" }, "page": { "description": "1-based page.", "type": "number" }, "radius_miles": { "description": "With location: include candidates within this many miles (e.g. 5, 10, 25, 50; max 100). Omit for exact-place matching.", "type": "number" }, "remote_ok": { "description": "Only candidates open to remote/hybrid.", "type": "boolean" }, "salary_max": { "type": "number" }, "salary_min": { "type": "number" }, "seniority_levels": { "description": "Seniority levels to match (any of): entry, junior, mid, senior, staff, principal, manager, director, executive.", "items": { "type": "string" }, "type": "array" }, "skills": { "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\").", "items": { "type": "string" }, "type": "array" }, "sort": { "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.", "enum": [ "recency", "skill_match" ], "type": "string" }, "updated_since": { "description": "ISO timestamp — only resumes updated since.", "type": "string" }, "work_authorization": { "description": "Filter by work authorization: \"authorized\" (no sponsorship needed) or \"sponsorship-required\".", "type": "string" }, "work_location_types": { "description": "Work-location preferences to match (any of): remote, hybrid, onsite.", "items": { "type": "string" }, "type": "array" } }, "type": "object" }, "name": "search_candidates", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:f39adf9288ed11a0fd08f907b2ded01b4c32a2d007b9cd276e71e9ac8b204cd7 | sha256sum