io.github.QueryQuarry/queryquarry
REMOTE · QUERYQUARRY.COM · SCANNED AUG 3
Double-blind talent marketplace: AIs search anonymous opted-in candidates; reveal on consent.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1623 tokens (~147/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · queryquarry.com
claude mcp add --transport http queryquarry-queryquarry https://queryquarry.com/api/mcp
[mcp_servers.queryquarry-queryquarry] url = "https://queryquarry.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"queryquarry-queryquarry": {
"type": "remote",
"url": "https://queryquarry.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add queryquarry-queryquarry --url https://queryquarry.com/api/mcp --transport streamable-http
mcp_servers:
queryquarry-queryquarry:
url: "https://queryquarry.com/api/mcp" {
"mcpServers": {
"queryquarry-queryquarry": {
"type": "http",
"url": "https://queryquarry.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://queryquarry.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=queryquarry.com | CN=WE1,O=Google Trust Services,C=US | 27 Jun 2026 | 25 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | cf51ba56fce3b4540e0b7b726a77feb0 |
| SANs: queryquarry.com, *.queryquarry.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of queryquarry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| queryquarry.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://queryquarry.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://queryquarry.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-Y2FiNDE2N2MtZjNjNC00YzAyLTk4N2MtODZmNmNlMjE1ODU0' 'strict-dynamic' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://xeycuypjhttwxjjazsos.supabase.co; media-src 'self' https://xeycuypjhttwxjjazsos.supabase.co; font-src 'self'; connect-src 'self' https://xeycuypjhttwxjjazsos.supabase.co wss://xeycuypjhttwxjjazsos.supabase.co https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Protected resource metadata
| Document | https://queryquarry.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://queryquarry.com/api/mcp |
| Authorisation server | https://secretive-swamp-9927.customers.stytch.dev |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://queryquarry.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://queryquarry.com/api/mcp | HTTPS enforced | 308 | https://queryquarry.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_subscription ~23
Check your subscription tier, status, rate limit, and usage this hour.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_candidate ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | — |
| resume_id | string | yes | — |
No output schema declared.
No examples provided.
get_contact ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | — | — |
| contact_id | string | — | — |
No output schema declared.
No examples provided.
get_corpus_stats ~25
Get aggregate stats about the talent corpus (counts, top skills/locations).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_docs ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_new_candidates ~47
Get resumes new or updated since a timestamp (your standing alert). Same filters as search_candidates. Call daily with yesterday's timestamp; no duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | ISO timestamp. |
No output schema declared.
No examples provided.
get_watchlist ~31
Get your saved candidates (watchlist).
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | — | — |
| status | string | — | — |
No output schema declared.
No examples provided.
report_contact_outcome ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | — | — |
| contact_id | string | — | — |
| outcome | string | yes | — |
No output schema declared.
No examples provided.
request_contact ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | — |
| message | string | yes | 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… |
| resume_id | string | yes | — |
No output schema declared.
No examples provided.
save_candidate ~43
Save a candidate resume to your watchlist with optional notes.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | — |
| notes | string | — | — |
| resume_id | string | yes | — |
No output schema declared.
No examples provided.
search_candidates ~578
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).
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | — | — |
| employment_types | array | — | Engagement types to match (any of): full-time, part-time, contract, freelance, internship. Synonyms/variants are normalized. |
| experience_years_max | number | — | — |
| experience_years_min | number | — | — |
| limit | number | — | Results per page (max 25). |
| 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. |
| open_to_relocation | boolean | — | Only candidates willing to relocate for the right role. |
| page | number | — | 1-based page. |
| radius_miles | number | — | With location: include candidates within this many miles (e.g. 5, 10, 25, 50; max 100). Omit for exact-place matching. |
| remote_ok | boolean | — | Only candidates open to remote/hybrid. |
| salary_max | number | — | — |
| salary_min | number | — | — |
| seniority_levels | array | — | Seniority levels to match (any of): entry, junior, mid, senior, staff, principal, manager, director, executive. |
| 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"). |
| 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 f… |
| updated_since | string | — | ISO timestamp — only resumes updated since. |
| 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. |
No output schema declared.
No examples provided.