Fairquery Agent Trust & Data Safety

com.getfairquery/agent-trust-mcpVersion 1.1.10

PII/secret redaction, email checks, sanctions screening, OSV lookups and an MCP server pre-check.

Status

Responds285 msNov 14, 2026, 13:58 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:58 UTC
Latency: 285 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.getfairquery.com/mcpResponds285 msNov 14, 2026, 13:58 UTC

No sign-in

Claude Code

claude mcp add --transport http agent-trust-mcp https://mcp.getfairquery.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: agent-trust-mcp
Remote MCP server URL: https://mcp.getfairquery.com/mcp

Cursor

{
  "mcpServers": {
    "agent-trust-mcp": {
      "url": "https://mcp.getfairquery.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"agent-trust-mcp","type":"http","url":"https://mcp.getfairquery.com/mcp"}'

Streamable HTTP

npm: @fairquery/agent-trust-mcp 1.1.10

Package only

npm (npx)

claude mcp add agent-trust-mcp -- npx -y @fairquery/agent-trust-mcp@1.1.10

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

21 tools

Tools of Fairquery Agent Trust & Data Safety
	Description		Read-only	Idempotent	Open world
`email_check_syntax`WHAT: Offline email checks: RFC-style syntax + normalization, common domain typo "did you mean" (gmial.com -> gmail.com), disposable/temporary domain (bundled CC0 list, ~thousands of domains), role account (info@, sales@), free webmail provider. WHEN: Fast pre-filtering of signups or lead lists, before paying for email_validate_deliverability. WHEN NOT: Does NOT check DNS/MX, so it cannot tell whether the domain receives mail; use email_validate_deliverability (paid) for MX/SPF/DMARC. COST: Free; no token. RETURNS: Paged "email_check" rows; verdict is invalid \| risky \| unknown, never valid (dns_checked is always false). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call (no DNS/SMTP); addresses are not forwarded. Synchronous and CPU-bound, no rate limits: 10,000 addresses (the per-call maximum) return in well under a second. PARAMETERS: emails: each element is parsed on its own (one address per element; a comma-separated list in one element is INVALID_SYNTAX, not split). Before checking, "Name <addr>" is reduced to addr, a leading "mailto:" is dropped, the domain is lowercased (local part keeps its case), a trailing dot is removed and IDN domains are converted to punycode; the normalized value is returned as email, the original as input. Duplicates are not merged: every element yields one row, in input order. Role detection ignores +tags (sales+eu@ counts as sales@) and disposable matching also covers subdomains of listed domains. limit/offset page those rows; meta.summary always counts verdicts over ALL rows, not just the current page. EXAMPLE: {"emails":["someone@gmial.com"]} -> verdict "risky", reasons ["POSSIBLE_TYPO","DNS_NOT_CHECKED"], did_you_mean "someone@gmail.com".	WHAT: Offline email checks: RFC-style syntax + normalization, common domain typo "did you mean" (gmial.com -> gmail.com), disposable/temporary domain (bundled CC0 list, ~thousands of domains), role account (info@, sales@), free webmail provider. WHEN: Fast pre-filtering of signups or lead lists, before paying for email_validate_deliverability. WHEN NOT: Does NOT check DNS/MX, so it cannot tell whether the domain receives mail; use email_validate_deliverability (paid) for MX/SPF/DMARC. COST: Free; no token. RETURNS: Paged "email_check" rows; verdict is invalid \| risky \| unknown, never valid (dns_checked is always false). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call (no DNS/SMTP); addresses are not forwarded. Synchronous and CPU-bound, no rate limits: 10,000 addresses (the per-call maximum) return in well under a second. PARAMETERS: emails: each element is parsed on its own (one address per element; a comma-separated list in one element is INVALID_SYNTAX, not split). Before checking, "Name <addr>" is reduced to addr, a leading "mailto:" is dropped, the domain is lowercased (local part keeps its case), a trailing dot is removed and IDN domains are converted to punycode; the normalized value is returned as email, the original as input. Duplicates are not merged: every element yields one row, in input order. Role detection ignores +tags (sales+eu@ counts as sales@) and disposable matching also covers subdomains of listed domains. limit/offset page those rows; meta.summary always counts verdicts over ALL rows, not just the current page. EXAMPLE: {"emails":["someone@gmial.com"]} -> verdict "risky", reasons ["POSSIBLE_TYPO","DNS_NOT_CHECKED"], did_you_mean "someone@gmail.com".	No	Yes	Yes	No
`email_validate_deliverability`WHAT: Runs the Fairquery Apify Actor email-validator-mx-disposable: syntax, domain existence, MX/null-MX, disposable, role, free provider, typo suggestion, SPF/DMARC policy, mail provider; final verdict valid \| risky \| invalid \| unknown. WHEN: Only when MX/DNS matters (can the domain receive mail?), e.g. cleaning lists before a send or verifying a lead's domain; pre-filter with email_check_syntax to avoid paying for obviously bad rows. WHEN NOT: Offline format, typo, disposable or role checks (free email_check_syntax). Leads that also need sanctions screening: trust_screen_lead (one merged decision). It does not SMTP-probe mailboxes. COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.79 per 1,000 emails (+ $0.05 per 1,000 runs). 100 emails ~ $0.08. RETURNS: Paged "email" rows (verdict valid \| risky \| invalid \| unknown with reasons[]) or "error" rows. Tool errors: APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. BEHAVIOR: No email is sent; results change only with live DNS. Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor in your account does the DNS/MX lookups. PARAMETERS: emails: elements may also hold comma/semicolon/newline-separated lists or "Name <addr>" forms; the Actor splits them, trims, and skips case-insensitive duplicates, so you pay once per unique address. The allow* flags only decide whether a condition downgrades the verdict to "risky": the matching reason code (ROLE_ACCOUNT, DISPOSABLE_DOMAIN, FREE_PROVIDER) is reported in reasons[] either way, and they can never turn an "invalid" address (bad syntax, no domain, null MX, no mail server) into "valid". POSSIBLE_TYPO and IMPLICIT_MX_ONLY always make it "risky" regardless of flags. Typical presets: B2B lead list = allowFreeProviders false + allowRoleAccounts false; consumer	WHAT: Runs the Fairquery Apify Actor email-validator-mx-disposable: syntax, domain existence, MX/null-MX, disposable, role, free provider, typo suggestion, SPF/DMARC policy, mail provider; final verdict valid \| risky \| invalid \| unknown. WHEN: Only when MX/DNS matters (can the domain receive mail?), e.g. cleaning lists before a send or verifying a lead's domain; pre-filter with email_check_syntax to avoid paying for obviously bad rows. WHEN NOT: Offline format, typo, disposable or role checks (free email_check_syntax). Leads that also need sanctions screening: trust_screen_lead (one merged decision). It does not SMTP-probe mailboxes. COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.79 per 1,000 emails (+ $0.05 per 1,000 runs). 100 emails ~ $0.08. RETURNS: Paged "email" rows (verdict valid \| risky \| invalid \| unknown with reasons[]) or "error" rows. Tool errors: APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. BEHAVIOR: No email is sent; results change only with live DNS. Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor in your account does the DNS/MX lookups. PARAMETERS: emails: elements may also hold comma/semicolon/newline-separated lists or "Name <addr>" forms; the Actor splits them, trims, and skips case-insensitive duplicates, so you pay once per unique address. The allow* flags only decide whether a condition downgrades the verdict to "risky": the matching reason code (ROLE_ACCOUNT, DISPOSABLE_DOMAIN, FREE_PROVIDER) is reported in reasons[] either way, and they can never turn an "invalid" address (bad syntax, no domain, null MX, no mail server) into "valid". POSSIBLE_TYPO and IMPLICIT_MX_ONLY always make it "risky" regardless of flags. Typical presets: B2B lead list = allowFreeProviders false + allowRoleAccounts false; consumer	No	Yes	Yes	Yes
`jobs_check_open`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Re-check ONE job on the employer's ATS right now and report open or closed. WHEN: Before applying, alerting or contacting about a specific job you got earlier (job_key or ats + slug + jobId), when you only need open or closed. WHEN NOT: One job's full detail (jobs_get_job). Listing a board (jobs_get_board). Checking many jobs at once (jobs_search_companies is offline here; this tool checks one job). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. The job id and board slug are sent to the public ATS host in the requests below. Greenhouse, Lever: one GET to the documented per-job endpoint; HTTP 404 = closed. Ashby, Personio, Pinpoint and Gem have no per-job read here, so the documented board feed is fetched once and searched for the id (method "board_listing"). Personio is robots.txt then /xml. Pinpoint is robots.txt then /postings.json. Gem is GET /job_posts/ only. No apply URL is requested. "open" means currently published by the employer; it does not prove the role is still being filled. COST: No APIFY_TOKEN, no billing. RETURNS: One "open_check" row (job = the full "job" row when includeDescription=true and the job is open, else null), or a tool error: INVALID_INPUT, BOARD_NOT_FOUND, HOST_BLOCKED or NETWORK_ERROR (the last two retryable). PARAMETERS: A malformed jobKey, or neither jobKey nor a complete ats + slug + jobId, returns INVALID_INPUT without	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Re-check ONE job on the employer's ATS right now and report open or closed. WHEN: Before applying, alerting or contacting about a specific job you got earlier (job_key or ats + slug + jobId), when you only need open or closed. WHEN NOT: One job's full detail (jobs_get_job). Listing a board (jobs_get_board). Checking many jobs at once (jobs_search_companies is offline here; this tool checks one job). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. The job id and board slug are sent to the public ATS host in the requests below. Greenhouse, Lever: one GET to the documented per-job endpoint; HTTP 404 = closed. Ashby, Personio, Pinpoint and Gem have no per-job read here, so the documented board feed is fetched once and searched for the id (method "board_listing"). Personio is robots.txt then /xml. Pinpoint is robots.txt then /postings.json. Gem is GET /job_posts/ only. No apply URL is requested. "open" means currently published by the employer; it does not prove the role is still being filled. COST: No APIFY_TOKEN, no billing. RETURNS: One "open_check" row (job = the full "job" row when includeDescription=true and the job is open, else null), or a tool error: INVALID_INPUT, BOARD_NOT_FOUND, HOST_BLOCKED or NETWORK_ERROR (the last two retryable). PARAMETERS: A malformed jobKey, or neither jobKey nor a complete ats + slug + jobId, returns INVALID_INPUT without	No	Yes	Yes	Yes
`jobs_find_board`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Resolve a company name, domain or careers/board URL to its public job board(s) on Greenhouse, Lever or Ashby. A Personio, Pinpoint or Gem URL (or personio:account, pinpoint:subdomain, gem:vanity) you already know is parsed on this Worker and not looked up. WHEN: Before jobs_get_board when you only know the company ("Ramp", "sentry.io", "https://stripe.com/jobs") or you have a Personio, Pinpoint or Gem career URL. WHEN NOT: The user asked for jobs in a place or by role and did not name a company. Call jobs_search_by_location. Do not ask them for a company and do not call this tool first. You already have ats + slug (call jobs_get_board). For many companies at once, paid indexed search is live (Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp); jobs_search_companies is offline here (not billed). It cannot find Workday, Workable, Recruitee, Rippling or LinkedIn pages, and it does not discover Personio, Pinpoint or Gem boards. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. Parts of the input are sent to public ATS hosts or the company site, as the steps below describe. Order: board-URL parsing (including personio:{account}, pinpoint:{subdomain}, gem:{vanity} and their public board URLs, no network) -> verified starter list -> the company's own website (only for a domain/URL input; robots.txt respected, <= 3 pages, priv	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Resolve a company name, domain or careers/board URL to its public job board(s) on Greenhouse, Lever or Ashby. A Personio, Pinpoint or Gem URL (or personio:account, pinpoint:subdomain, gem:vanity) you already know is parsed on this Worker and not looked up. WHEN: Before jobs_get_board when you only know the company ("Ramp", "sentry.io", "https://stripe.com/jobs") or you have a Personio, Pinpoint or Gem career URL. WHEN NOT: The user asked for jobs in a place or by role and did not name a company. Call jobs_search_by_location. Do not ask them for a company and do not call this tool first. You already have ats + slug (call jobs_get_board). For many companies at once, paid indexed search is live (Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp); jobs_search_companies is offline here (not billed). It cannot find Workday, Workable, Recruitee, Rippling or LinkedIn pages, and it does not discover Personio, Pinpoint or Gem boards. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. Parts of the input are sent to public ATS hosts or the company site, as the steps below describe. Order: board-URL parsing (including personio:{account}, pinpoint:{subdomain}, gem:{vanity} and their public board URLs, no network) -> verified starter list -> the company's own website (only for a domain/URL input; robots.txt respected, <= 3 pages, priv	No	Yes	Yes	Yes
`jobs_get_board`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Fetch every job currently published on ONE company board from its official public ATS API (Greenhouse, Lever or Ashby), from Personio's documented XML feed, from Pinpoint's documented postings.json, or from a named Gem job board, normalize it and filter it on this Worker. WHEN: You know the board (ats + slug), e.g. from jobs_find_board or a careers-page link, and want its live openings now. For Personio, Pinpoint and Gem you already know the company account, subdomain or vanity. WHEN NOT: One known job's full detail (jobs_get_job). Jobs in a place or by role across the starter list, without a company name (jobs_search_by_location). Do not ask the user for a company and do not call this tool or jobs_find_board first for that ask. Many companies at once, history (new/closed/reposted since last run), or careers-page discovery at scale: use paid indexed search (Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp, your own Apify token). jobs_search_companies is offline here and not billed. Use jobs_search_by_location for a place or role on the 135 starter boards. Unknown Greenhouse/Lever/Ashby board: use jobs_find_board first. Personio, Pinpoint and Gem are never discovered. SmartRecruiters, LinkedIn, Workday, Workable, Recruitee and Rippling are not supported and never contacted. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or resu	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Fetch every job currently published on ONE company board from its official public ATS API (Greenhouse, Lever or Ashby), from Personio's documented XML feed, from Pinpoint's documented postings.json, or from a named Gem job board, normalize it and filter it on this Worker. WHEN: You know the board (ats + slug), e.g. from jobs_find_board or a careers-page link, and want its live openings now. For Personio, Pinpoint and Gem you already know the company account, subdomain or vanity. WHEN NOT: One known job's full detail (jobs_get_job). Jobs in a place or by role across the starter list, without a company name (jobs_search_by_location). Do not ask the user for a company and do not call this tool or jobs_find_board first for that ask. Many companies at once, history (new/closed/reposted since last run), or careers-page discovery at scale: use paid indexed search (Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp, your own Apify token). jobs_search_companies is offline here and not billed. Use jobs_search_by_location for a place or role on the 135 starter boards. Unknown Greenhouse/Lever/Ashby board: use jobs_find_board first. Personio, Pinpoint and Gem are never discovered. SmartRecruiters, LinkedIn, Workday, Workable, Recruitee and Rippling are not supported and never contacted. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or resu	No	Yes	Yes	Yes
`jobs_get_job`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Fetch the full detail of ONE job that is currently published on its official public ATS API (Greenhouse, Lever or Ashby), a Personio or Pinpoint feed, or a named Gem job board, normalized the same way as a board listing. WHEN: You already have a job_key, or ats + slug + jobId, from jobs_get_board or a board link and need that single job's text, location, compensation and dates. On Gem the row links to jobs.gem.com and does not include the ad body. WHEN NOT: Open or closed only (jobs_check_open). Every opening on a board (jobs_get_board). Jobs in a place across the starter list with no company name (jobs_search_by_location). Many companies at once (paid indexed search: Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp; jobs_search_companies is offline here and not billed). SmartRecruiters, LinkedIn, Workday, Workable, Recruitee and Rippling are not supported and never contacted. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. The job id and board slug are sent to the public ATS host in the requests below. Greenhouse and Lever: one GET to the documented per-job endpoint (the description is in that response). Ashby, Personio, Pinpoint and Gem have no per-job read here: the documented board feed is fetched once and the id is looked up. Personio is robots.txt then /xml. Pinpoint is robots.txt then /postings.json. Gem is G	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Fetch the full detail of ONE job that is currently published on its official public ATS API (Greenhouse, Lever or Ashby), a Personio or Pinpoint feed, or a named Gem job board, normalized the same way as a board listing. WHEN: You already have a job_key, or ats + slug + jobId, from jobs_get_board or a board link and need that single job's text, location, compensation and dates. On Gem the row links to jobs.gem.com and does not include the ad body. WHEN NOT: Open or closed only (jobs_check_open). Every opening on a board (jobs_get_board). Jobs in a place across the starter list with no company name (jobs_search_by_location). Many companies at once (paid indexed search: Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp; jobs_search_companies is offline here and not billed). SmartRecruiters, LinkedIn, Workday, Workable, Recruitee and Rippling are not supported and never contacted. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. The job id and board slug are sent to the public ATS host in the requests below. Greenhouse and Lever: one GET to the documented per-job endpoint (the description is in that response). Ashby, Personio, Pinpoint and Gem have no per-job read here: the documented board feed is fetched once and the id is looked up. Personio is robots.txt then /xml. Pinpoint is robots.txt then /postings.json. Gem is G	No	Yes	Yes	Yes
`jobs_list_seed_boards`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: List the bundled starter list of company job boards that Fairquery verified on their official ATS APIs (company, domain, ats, slug, verified_at, jobs_at_verification). WHEN: To pick companies to scan, or to know which names jobs_find_board resolves instantly. WHEN NOT: Live jobs on one board (jobs_get_board), a place search across this list (jobs_search_by_location), or companies not in the list (jobs_find_board). The list is a starting point (135 boards), not the paid indexed search (8,800+ boards, Apify Actor fairquery/jobs-index-search). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. No further network call: it reads a static list compiled into this Worker. jobs_at_verification is a snapshot from verified_at and goes stale. COST: No APIFY_TOKEN, no billing. RETURNS: Paged "seed_board" rows in the fixed bundled order (original boards stay first, so earlier offsets stay put). 135 Greenhouse, Lever and Ashby boards. PARAMETERS: ats narrows the list; omit it for the whole starter list (Greenhouse, Lever, Ashby). Personio, Pinpoint and Gem are not in the starter list (named accounts only). meta.by_ats always counts the whole list per ATS and ignores ats, so take paging totals from total. Feed ats + slug of any item straight into jobs_get_board. EXAMPLE: {"ats":"lever"} -> Palantir, Spotify, Zoox, Ro, then more Lever boards.	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: List the bundled starter list of company job boards that Fairquery verified on their official ATS APIs (company, domain, ats, slug, verified_at, jobs_at_verification). WHEN: To pick companies to scan, or to know which names jobs_find_board resolves instantly. WHEN NOT: Live jobs on one board (jobs_get_board), a place search across this list (jobs_search_by_location), or companies not in the list (jobs_find_board). The list is a starting point (135 boards), not the paid indexed search (8,800+ boards, Apify Actor fairquery/jobs-index-search). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. No further network call: it reads a static list compiled into this Worker. jobs_at_verification is a snapshot from verified_at and goes stale. COST: No APIFY_TOKEN, no billing. RETURNS: Paged "seed_board" rows in the fixed bundled order (original boards stay first, so earlier offsets stay put). 135 Greenhouse, Lever and Ashby boards. PARAMETERS: ats narrows the list; omit it for the whole starter list (Greenhouse, Lever, Ashby). Personio, Pinpoint and Gem are not in the starter list (named accounts only). meta.by_ats always counts the whole list per ATS and ignores ats, so take paging totals from total. Feed ats + slug of any item straight into jobs_get_board. EXAMPLE: {"ats":"lever"} -> Palantir, Spotify, Zoox, Ro, then more Lever boards.	No	Yes	Yes	No
`jobs_search_by_location`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Free search of the bundled starter list (135 public Greenhouse, Lever and Ashby boards). Not every employer and not every company. No company name. Live jobs from each board's official public API. Same normalized "job" rows as jobs_get_board. One call may cover only part of the list. WHEN: The user asks for jobs by place and/or role and does not name a company. Call THIS tool immediately. Do not ask the user for a company. Do not call jobs_get_board or jobs_find_board first. Examples: "avionics jobs in Baltimore MD", "avionics jobs in Costa Mesa", "remote RN jobs in PA", "nursing jobs in Maryland". Put the place in locations (Baltimore, Baltimore MD, MD, Maryland, BWI, PA, Costa Mesa) or countries, or set remote to "only". Put a skill or role that may not be the job title in descriptionIncludes (avionics, nurse), not in titleIncludes. WHEN NOT: The user already named one company or board (jobs_find_board, then jobs_get_board). They want employers outside this starter list, radius or salary filters: paid indexed search (8,800+ boards, fresh daily index) is live as the Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp (own Apify token). jobs_search_companies is offline here and does not run any paid Actor. This tool does not search all companies. The free limits stay 135 starter boards. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inp	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Free search of the bundled starter list (135 public Greenhouse, Lever and Ashby boards). Not every employer and not every company. No company name. Live jobs from each board's official public API. Same normalized "job" rows as jobs_get_board. One call may cover only part of the list. WHEN: The user asks for jobs by place and/or role and does not name a company. Call THIS tool immediately. Do not ask the user for a company. Do not call jobs_get_board or jobs_find_board first. Examples: "avionics jobs in Baltimore MD", "avionics jobs in Costa Mesa", "remote RN jobs in PA", "nursing jobs in Maryland". Put the place in locations (Baltimore, Baltimore MD, MD, Maryland, BWI, PA, Costa Mesa) or countries, or set remote to "only". Put a skill or role that may not be the job title in descriptionIncludes (avionics, nurse), not in titleIncludes. WHEN NOT: The user already named one company or board (jobs_find_board, then jobs_get_board). They want employers outside this starter list, radius or salary filters: paid indexed search (8,800+ boards, fresh daily index) is live as the Apify Actor fairquery/jobs-index-search or https://mcp.getfairquery.com/jobs-index/mcp (own Apify token). jobs_search_companies is offline here and does not run any paid Actor. This tool does not search all companies. The free limits stay 135 starter boards. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inp	No	Yes	Yes	Yes
`jobs_search_companies`Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Offline on this free server. Paid indexed Jobs search is live elsewhere: the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp, on your own Apify token. One call searches 8,800+ Greenhouse, Ashby and Lever boards with radius and salary filters from a fresh daily index. This tool does not run any Actor. WHEN: Do not call this for jobs. For many companies, radius or salary filters, point the user to the Actor or MCP above (Apify token from https://console.apify.com/settings/integrations; new accounts get a $5 starter credit). For free jobs by place or role, call jobs_search_by_location (135 starter boards, no token). WHEN NOT: Any live lookup. One board (jobs_get_board). A place or role on the starter list (jobs_search_by_location — call that; do not ask for a company). One job's full detail (jobs_get_job), or one open/closed re-check (jobs_check_open). BEHAVIOR: Returns COMING_SOON immediately on this Fairquery-hosted Worker. Does not read an Apify token from the request, does not call Apify, and does not start an Actor run, whether or not a token is sent. Arguments are ignored. Nothing is billed. Free tools keep working with no token. COST: Not billed. No Actor run. Indexed search bills the caller's own Apify account on the Actor or MCP above, never through this free server. RETURNS: Tool error COMING_SOON (retryable false, kept as the error code) and no job rows. The message says indexed search is live, links the Acto	Indexed Jobs search is LIVE (paid, on your own Apify token): one call searches 8,800+ Greenhouse, Ashby and Lever company boards, with radius and salary filters, from a fresh daily index (not a live scrape of a few boards). Run it as the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp (send your Apify token). New Apify accounts get a $5 starter credit. This free tool stays free and live-scans the 135-board starter list. WHAT: Offline on this free server. Paid indexed Jobs search is live elsewhere: the Apify Actor https://apify.com/fairquery/jobs-index-search or the MCP https://mcp.getfairquery.com/jobs-index/mcp, on your own Apify token. One call searches 8,800+ Greenhouse, Ashby and Lever boards with radius and salary filters from a fresh daily index. This tool does not run any Actor. WHEN: Do not call this for jobs. For many companies, radius or salary filters, point the user to the Actor or MCP above (Apify token from https://console.apify.com/settings/integrations; new accounts get a $5 starter credit). For free jobs by place or role, call jobs_search_by_location (135 starter boards, no token). WHEN NOT: Any live lookup. One board (jobs_get_board). A place or role on the starter list (jobs_search_by_location — call that; do not ask for a company). One job's full detail (jobs_get_job), or one open/closed re-check (jobs_check_open). BEHAVIOR: Returns COMING_SOON immediately on this Fairquery-hosted Worker. Does not read an Apify token from the request, does not call Apify, and does not start an Actor run, whether or not a token is sent. Arguments are ignored. Nothing is billed. Free tools keep working with no token. COST: Not billed. No Actor run. Indexed search bills the caller's own Apify account on the Actor or MCP above, never through this free server. RETURNS: Tool error COMING_SOON (retryable false, kept as the error code) and no job rows. The message says indexed search is live, links the Acto	No	Yes	Yes	No
`mcp_server_precheck`WHAT: Pre-install check for one MCP server. Scans tool names (split on _ - . and camelCase), descriptions, parameter names/descriptions and schema enum/default/examples you pass for injection phrasing, concealed characters (tag characters, base64 and hex blobs are decoded and rescanned), hidden markup, cross-server references, shadowing of other tools in the same list (same sentence; plain ordering like "call X first" is not flagged), and exfil destinations (email/URL/public IP/paste site next to send/post/upload/copy/forward/BCC, or stealth wording + action + user data). Optional baseline compares SHA-256 fingerprints with a prior scan (rug pull). Optional sarif=true adds a SARIF 2.1.0 log. An MCPB manifest in toolsListJson also has its server.mcp_config command checked for download-and-pipe-to-shell, and its server.mcp_config / mcpServers env, headers, args and url checked for hardcoded secrets (same detectors as mcpConfig, masked). Also flags shell/exec tools and unrestricted file paths (OVERBROAD_PERMISSION), near-miss tool or package names (TYPOSQUAT), and with servers[] the private-data + untrusted-input + external-send combination across servers (TOXIC_FLOW). Injection and exfil phrasing is also matched in Spanish, French, German, Portuguese, Italian and Dutch. The same rules also run on prompts, resources and SKILL.md text you pass (skillMd shell blocks are checked for download-and-pipe-to-shell), and serverUrl fetches a remote server's tools/list for you. mcpConfig (a pasted mcp.json / claude_desktop_config.json / env block) is checked for hardcoded secrets and personal data with the pii_scan_text detectors (credential hygiene; values are masked, nothing is forwarded). Every result has meta.grade, an A-F letter for non-technical readers, labelled meta.grade_label "Static checks: A": it reflects deterministic pattern checks only; semantic analysis is not run. Limitation: this free tier does not detect instructions reworded to avoid known phrasing (paraphrase	WHAT: Pre-install check for one MCP server. Scans tool names (split on _ - . and camelCase), descriptions, parameter names/descriptions and schema enum/default/examples you pass for injection phrasing, concealed characters (tag characters, base64 and hex blobs are decoded and rescanned), hidden markup, cross-server references, shadowing of other tools in the same list (same sentence; plain ordering like "call X first" is not flagged), and exfil destinations (email/URL/public IP/paste site next to send/post/upload/copy/forward/BCC, or stealth wording + action + user data). Optional baseline compares SHA-256 fingerprints with a prior scan (rug pull). Optional sarif=true adds a SARIF 2.1.0 log. An MCPB manifest in toolsListJson also has its server.mcp_config command checked for download-and-pipe-to-shell, and its server.mcp_config / mcpServers env, headers, args and url checked for hardcoded secrets (same detectors as mcpConfig, masked). Also flags shell/exec tools and unrestricted file paths (OVERBROAD_PERMISSION), near-miss tool or package names (TYPOSQUAT), and with servers[] the private-data + untrusted-input + external-send combination across servers (TOXIC_FLOW). Injection and exfil phrasing is also matched in Spanish, French, German, Portuguese, Italian and Dutch. The same rules also run on prompts, resources and SKILL.md text you pass (skillMd shell blocks are checked for download-and-pipe-to-shell), and serverUrl fetches a remote server's tools/list for you. mcpConfig (a pasted mcp.json / claude_desktop_config.json / env block) is checked for hardcoded secrets and personal data with the pii_scan_text detectors (credential hygiene; values are masked, nothing is forwarded). Every result has meta.grade, an A-F letter for non-technical readers, labelled meta.grade_label "Static checks: A": it reflects deterministic pattern checks only; semantic analysis is not run. Limitation: this free tier does not detect instructions reworded to avoid known phrasing (paraphrase	No	Yes	Yes	Yes
`osv_audit_dependencies`WHAT: Runs the Fairquery Apify Actor osv-dependency-vulnerability-check: parses package.json, package-lock.json (v1-v3), requirements.txt or go.mod (or a package list), checks OSV, and returns per-package max severity/CVSS, fixed versions, a recommended upgrade version and one row per vulnerability (deduped aliases). WHEN: Only for manifests, severity filtering or fix recommendations: full project audits from a pasted manifest, CI-style reports; for a few exact versions use osv_query_packages (free). WHEN NOT: Quick checks of a few exact versions (osv_query_packages, free) or one advisory (osv_get_vulnerability, free). COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.50 per 1,000 packages + $1.50 per 1,000 vulnerabilities found (+ $0.05 per 1,000 runs). Use minSeverity="HIGH" to cut vuln rows. lodash+django (2 pkgs, 41 vulns) ~ $0.06. RETURNS: Paged rows type="package" (vulnerable, vuln_count, max_severity, fixed_versions, recommended_version), type="vulnerability" (id, cve_ids, severity, cvss_score, fixed_versions, osv_url) or type="error". Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. BEHAVIOR: Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor in your account queries OSV.dev. Up to 1000 packages or a 2,000,000-char manifest. PARAMETERS: packages or manifestText = input (one required); manifestType = format, default auto-detect; minSeverity = only report at/above ALL\|LOW\|MEDIUM\|HIGH\|CRITICAL (default ALL); includeDevDependencies (default true); limit = page size (default 100, max 1000); offset = items to skip for paging (default 0). EXAMPLE: {"manifestText":"django==3.2.0\nrequests==2.19.0","minSeverity":"HIGH"}	WHAT: Runs the Fairquery Apify Actor osv-dependency-vulnerability-check: parses package.json, package-lock.json (v1-v3), requirements.txt or go.mod (or a package list), checks OSV, and returns per-package max severity/CVSS, fixed versions, a recommended upgrade version and one row per vulnerability (deduped aliases). WHEN: Only for manifests, severity filtering or fix recommendations: full project audits from a pasted manifest, CI-style reports; for a few exact versions use osv_query_packages (free). WHEN NOT: Quick checks of a few exact versions (osv_query_packages, free) or one advisory (osv_get_vulnerability, free). COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.50 per 1,000 packages + $1.50 per 1,000 vulnerabilities found (+ $0.05 per 1,000 runs). Use minSeverity="HIGH" to cut vuln rows. lodash+django (2 pkgs, 41 vulns) ~ $0.06. RETURNS: Paged rows type="package" (vulnerable, vuln_count, max_severity, fixed_versions, recommended_version), type="vulnerability" (id, cve_ids, severity, cvss_score, fixed_versions, osv_url) or type="error". Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. BEHAVIOR: Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor in your account queries OSV.dev. Up to 1000 packages or a 2,000,000-char manifest. PARAMETERS: packages or manifestText = input (one required); manifestType = format, default auto-detect; minSeverity = only report at/above ALL\|LOW\|MEDIUM\|HIGH\|CRITICAL (default ALL); includeDevDependencies (default true); limit = page size (default 100, max 1000); offset = items to skip for paging (default 0). EXAMPLE: {"manifestText":"django==3.2.0\nrequests==2.19.0","minSeverity":"HIGH"}	No	Yes	Yes	Yes
`osv_get_vulnerability`WHAT: Fetch full OSV records (summary, details, aliases, severity vectors, affected ranges, fixed versions, references) for advisory IDs from api.osv.dev. WHEN: You have IDs (from osv_query_packages or a report) and need details or the fixed version. WHEN NOT: To find which vulns affect a package version (osv_query_packages) or a whole manifest (osv_audit_dependencies, paid). COST: Free; no token. Advisory IDs leave the client, are received by this Worker, and are forwarded to api.osv.dev. Nothing is sent to Apify. This Worker's code is designed not to store inputs or results. RETURNS: Paged "vulnerability" rows with the raw OSV record fields, or "error" rows (VULN_NOT_FOUND \| OSV_FETCH_FAILED, see PARAMETERS). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. One HTTPS call per ID to api.osv.dev, in parallel; typically <2 s, 20 s timeout each. PARAMETERS: ids: each ID is fetched separately and yields exactly one row in input order, so one bad ID never fails the others: an unknown ID returns a VULN_NOT_FOUND row (not retryable), a network/5xx problem an OSV_FETCH_FAILED row (retryable - retry just that ID). Prefer the ecosystem/GHSA IDs returned by osv_query_packages (vuln_ids); a CVE-... ID only resolves when OSV indexes that CVE as its own record, otherwise look up the GHSA alias. IDs are matched as given (no trimming of URLs or prefixes), and duplicates are fetched twice. limit/offset only page the returned rows; every call re-fetches all given IDs, so for a next page resend the same ids with offset = nextOffset. EXAMPLE: {"ids":["GHSA-35jh-r3h4-6jhm"]} -> lodash command injection, fixed in 4.17.21.	WHAT: Fetch full OSV records (summary, details, aliases, severity vectors, affected ranges, fixed versions, references) for advisory IDs from api.osv.dev. WHEN: You have IDs (from osv_query_packages or a report) and need details or the fixed version. WHEN NOT: To find which vulns affect a package version (osv_query_packages) or a whole manifest (osv_audit_dependencies, paid). COST: Free; no token. Advisory IDs leave the client, are received by this Worker, and are forwarded to api.osv.dev. Nothing is sent to Apify. This Worker's code is designed not to store inputs or results. RETURNS: Paged "vulnerability" rows with the raw OSV record fields, or "error" rows (VULN_NOT_FOUND \| OSV_FETCH_FAILED, see PARAMETERS). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. One HTTPS call per ID to api.osv.dev, in parallel; typically <2 s, 20 s timeout each. PARAMETERS: ids: each ID is fetched separately and yields exactly one row in input order, so one bad ID never fails the others: an unknown ID returns a VULN_NOT_FOUND row (not retryable), a network/5xx problem an OSV_FETCH_FAILED row (retryable - retry just that ID). Prefer the ecosystem/GHSA IDs returned by osv_query_packages (vuln_ids); a CVE-... ID only resolves when OSV indexes that CVE as its own record, otherwise look up the GHSA alias. IDs are matched as given (no trimming of URLs or prefixes), and duplicates are fetched twice. limit/offset only page the returned rows; every call re-fetches all given IDs, so for a next page resend the same ids with offset = nextOffset. EXAMPLE: {"ids":["GHSA-35jh-r3h4-6jhm"]} -> lodash command injection, fixed in 4.17.21.	No	Yes	Yes	Yes
`osv_query_packages`WHAT: Query the public OSV.dev database (api.osv.dev querybatch) for exact package versions; returns which are vulnerable and the advisory IDs. WHEN: Quick "is lodash 4.17.20 vulnerable?" checks for up to 200 packages; then osv_get_vulnerability for details of specific IDs. WHEN NOT: Parsing manifests/lockfiles, severity filtering, fixed/recommended versions in one shot -> osv_audit_dependencies (paid). COST: Free; no token. Package names and versions leave the client, are received by this Worker, and are forwarded to api.osv.dev. Nothing is sent to Apify. This Worker's code is designed not to store inputs or results. RETURNS: Paged "package" rows (vulnerable, vuln_ids) or per-entry INVALID_ECOSYSTEM "error" rows. Tool errors: OSV_FETCH_FAILED (retryable). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. One HTTPS request to api.osv.dev (Google-run public API) for all packages; typically <2 s, 20 s timeout. Results change only when OSV publishes advisories. PARAMETERS: packages: each entry is checked independently and returns exactly one row, in input order. An unknown ecosystem yields a per-entry INVALID_ECOSYSTEM error row while the other entries still run. A version range such as "^4.17.0" or ">=2" is not resolved and normally returns no vulnerabilities (a false "safe"), so pin versions from your lockfile first. Duplicate entries are queried and returned twice. limit/offset page the rows (all packages are sent to OSV in a single request); meta.vulnerable_count counts all packages, not only the page. EXAMPLE: {"packages":[{"ecosystem":"npm","name":"lodash","version":"4.17.20"}]} -> vulnerable true, vuln_ids ["GHSA-35jh-r3h4-6jhm",...].	WHAT: Query the public OSV.dev database (api.osv.dev querybatch) for exact package versions; returns which are vulnerable and the advisory IDs. WHEN: Quick "is lodash 4.17.20 vulnerable?" checks for up to 200 packages; then osv_get_vulnerability for details of specific IDs. WHEN NOT: Parsing manifests/lockfiles, severity filtering, fixed/recommended versions in one shot -> osv_audit_dependencies (paid). COST: Free; no token. Package names and versions leave the client, are received by this Worker, and are forwarded to api.osv.dev. Nothing is sent to Apify. This Worker's code is designed not to store inputs or results. RETURNS: Paged "package" rows (vulnerable, vuln_ids) or per-entry INVALID_ECOSYSTEM "error" rows. Tool errors: OSV_FETCH_FAILED (retryable). BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. One HTTPS request to api.osv.dev (Google-run public API) for all packages; typically <2 s, 20 s timeout. Results change only when OSV publishes advisories. PARAMETERS: packages: each entry is checked independently and returns exactly one row, in input order. An unknown ecosystem yields a per-entry INVALID_ECOSYSTEM error row while the other entries still run. A version range such as "^4.17.0" or ">=2" is not resolved and normally returns no vulnerabilities (a false "safe"), so pin versions from your lockfile first. Duplicate entries are queried and returned twice. limit/offset page the rows (all packages are sent to OSV in a single request); meta.vulnerable_count counts all packages, not only the page. EXAMPLE: {"packages":[{"ecosystem":"npm","name":"lodash","version":"4.17.20"}]} -> vulnerable true, vuln_ids ["GHSA-35jh-r3h4-6jhm",...].	No	Yes	Yes	Yes
`pii_guard_documents`WHAT: Runs the Fairquery Apify Actor llm-data-guard-pii-secrets: everything pii_scan_text does PLUS person-name/location NER, street addresses, public document URLs (txt/md/json/csv/HTML/PDF text layer, <= 10 MB) and restore mode (put originals back into LLM output using a placeholder map). WHEN: Only when you need NER names/addresses, files at URLs/PDFs, or the hosted pipeline. WHEN NOT: Plain text scans (pii_scan_text / pii_redact_text, free), restoring placeholders in an LLM answer (pii_restore_text, free, same result as restore mode), images (no OCR), email deliverability. COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $1.50 per 1,000 documents + $0.20 per 1,000 findings. Example: 10 docs with 20 findings ~ $0.02. RETURNS: Paged "document" rows (findings masked; output_text in redact/restore modes; with returnPlaceholderMap the map comes back as an encrypted sealed_map string when this deployment has a seal key) or "error" rows. Tool errors: APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT, INPUT_EMPTY. BEHAVIOR: Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor runs in your Apify account and may fetch documentUrls. Up to 1000 texts / 100 URLs (10 MB each). PARAMETERS: texts and/or documentUrls: at least one non-empty (the schema marks both optional; neither -> INPUT_EMPTY, not billed); both may be combined and each text or URL becomes one billed document row. mode="restore" ignores all detector flags; with sealedMap it follows the same restore key rule as pii_restore_text (refusal -> RESTORE_KEY_REQUIRED, nothing billed); a clear-text placeholderMap alone is refused on deployments with a seal key (SEALED_MAP_REQUIRED, nothing billed); a placeholder missing from placeholderMap stays as is. Cost scales with documents and findings, so	WHAT: Runs the Fairquery Apify Actor llm-data-guard-pii-secrets: everything pii_scan_text does PLUS person-name/location NER, street addresses, public document URLs (txt/md/json/csv/HTML/PDF text layer, <= 10 MB) and restore mode (put originals back into LLM output using a placeholder map). WHEN: Only when you need NER names/addresses, files at URLs/PDFs, or the hosted pipeline. WHEN NOT: Plain text scans (pii_scan_text / pii_redact_text, free), restoring placeholders in an LLM answer (pii_restore_text, free, same result as restore mode), images (no OCR), email deliverability. COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $1.50 per 1,000 documents + $0.20 per 1,000 findings. Example: 10 docs with 20 findings ~ $0.02. RETURNS: Paged "document" rows (findings masked; output_text in redact/restore modes; with returnPlaceholderMap the map comes back as an encrypted sealed_map string when this deployment has a seal key) or "error" rows. Tool errors: APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT, INPUT_EMPTY. BEHAVIOR: Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor runs in your Apify account and may fetch documentUrls. Up to 1000 texts / 100 URLs (10 MB each). PARAMETERS: texts and/or documentUrls: at least one non-empty (the schema marks both optional; neither -> INPUT_EMPTY, not billed); both may be combined and each text or URL becomes one billed document row. mode="restore" ignores all detector flags; with sealedMap it follows the same restore key rule as pii_restore_text (refusal -> RESTORE_KEY_REQUIRED, nothing billed); a clear-text placeholderMap alone is refused on deployments with a seal key (SEALED_MAP_REQUIRED, nothing billed); a placeholder missing from placeholderMap stays as is. Cost scales with documents and findings, so	No	Yes	Yes	Yes
`pii_list_detectors`WHAT: Fortress Shield (agent I/O PII protection). Catalog of every PII and secret entity type, which ones the free tools run on this Worker (pii_scan_text / pii_redact_text) vs only in the paid Actor (NER names/locations, and fetching remote PDF/document URLs; http(s) URLs in text are detected locally; STREET_ADDRESS patterns run locally with detectAddresses), redaction styles, sealed-map support, and the price of every paid tool in this server. WHEN: Before pii_scan_text / pii_redact_text to pick entityTypes, or to explain coverage and costs to a user. WHEN NOT: To actually scan text (pii_scan_text) or redact it (pii_redact_text). COST: Free; no token. RETURNS: One catalog object; local:true marks the detectors the free tools run (see PARAMETERS). features.sealed_map.available says whether this deployment can seal placeholder maps. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call; the catalog is compiled into this Worker, instant (<10 ms). No rate limits. PARAMETERS: None: call with an empty object {}; the catalog is always complete and cannot be filtered. Its output feeds other tools' parameters: copy detector "type" values verbatim into entityTypes of pii_scan_text / pii_redact_text (only rows with local:true can match there) or pii_guard_documents (all rows, incl. PERSON / LOCATION / STREET_ADDRESS); redaction_styles keys are the allowed redactionStyle values. EXAMPLE: {} -> {"detectors":[{"type":"AWS_ACCESS_KEY","category":"secret","local":true},...]}	WHAT: Fortress Shield (agent I/O PII protection). Catalog of every PII and secret entity type, which ones the free tools run on this Worker (pii_scan_text / pii_redact_text) vs only in the paid Actor (NER names/locations, and fetching remote PDF/document URLs; http(s) URLs in text are detected locally; STREET_ADDRESS patterns run locally with detectAddresses), redaction styles, sealed-map support, and the price of every paid tool in this server. WHEN: Before pii_scan_text / pii_redact_text to pick entityTypes, or to explain coverage and costs to a user. WHEN NOT: To actually scan text (pii_scan_text) or redact it (pii_redact_text). COST: Free; no token. RETURNS: One catalog object; local:true marks the detectors the free tools run (see PARAMETERS). features.sealed_map.available says whether this deployment can seal placeholder maps. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call; the catalog is compiled into this Worker, instant (<10 ms). No rate limits. PARAMETERS: None: call with an empty object {}; the catalog is always complete and cannot be filtered. Its output feeds other tools' parameters: copy detector "type" values verbatim into entityTypes of pii_scan_text / pii_redact_text (only rows with local:true can match there) or pii_guard_documents (all rows, incl. PERSON / LOCATION / STREET_ADDRESS); redaction_styles keys are the allowed redactionStyle values. EXAMPLE: {} -> {"detectors":[{"type":"AWS_ACCESS_KEY","category":"secret","local":true},...]}	No	Yes	Yes	No
`pii_redact_text`WHAT: Fortress Shield (agent I/O PII protection). Return sanitized copies of texts with every local PII/secret finding replaced: placeholder [EMAIL_k7q2m9xp4a] (random id per value), mask, or hash. For placeholders the originals come back only inside meta.sealed_map, an AES-256-GCM encrypted string that this Worker opens in pii_restore_text. The originals stay out of the model context. WHEN: Right before sending user data to an LLM/third party. Keep meta.sealed_map if you need to restore originals in the LLM answer later. WHEN NOT: For a findings report only use pii_scan_text. For unlabelled names (NER) or fetching PDFs and remote documents use pii_guard_documents (paid). http(s) URLs in text you already have are redacted here for free. COST: Free; no token. RETURNS: One "redacted_document" row per text with output_text, typed_placeholders_escaped, context_lowered, context_suppressed, below_threshold, context_report, field_paths (JSON input) and, with failClosed, blocked / block_reasons (output_text null); meta.audit, meta.secret_guidance, meta.compliance, meta.would_fail_closed; meta.sealed_map (placeholder style, "fqs2.…"; null plus a SEAL_KEY_NOT_CONFIGURED note when this deployment has no seal key) and meta.seal {algorithm, entries, expires_at, restore_bound, max_restores}. Errors: INPUT_TOO_LARGE, INVALID_PATTERN, INVALID_ARGUMENT, SEALED_MAP_INVALID, SEALED_MAP_EXPIRED, SEAL_KEY_NOT_CONFIGURED, RESTORE_KEY_REQUIRED / RESTORE_KEY_MISMATCH (priorSealedMap bound to another restore key). BEHAVIOR: Placeholder ids are random on every call unless you pass priorSealedMap; "hash" is random per call unless a hash key is set. The sealed_map is bound to the restore key header of this request (X-FQ-PII-Restore-Key, set by the operator in the client connection); without one, pii_restore_text reports counts only. Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, result	WHAT: Fortress Shield (agent I/O PII protection). Return sanitized copies of texts with every local PII/secret finding replaced: placeholder [EMAIL_k7q2m9xp4a] (random id per value), mask, or hash. For placeholders the originals come back only inside meta.sealed_map, an AES-256-GCM encrypted string that this Worker opens in pii_restore_text. The originals stay out of the model context. WHEN: Right before sending user data to an LLM/third party. Keep meta.sealed_map if you need to restore originals in the LLM answer later. WHEN NOT: For a findings report only use pii_scan_text. For unlabelled names (NER) or fetching PDFs and remote documents use pii_guard_documents (paid). http(s) URLs in text you already have are redacted here for free. COST: Free; no token. RETURNS: One "redacted_document" row per text with output_text, typed_placeholders_escaped, context_lowered, context_suppressed, below_threshold, context_report, field_paths (JSON input) and, with failClosed, blocked / block_reasons (output_text null); meta.audit, meta.secret_guidance, meta.compliance, meta.would_fail_closed; meta.sealed_map (placeholder style, "fqs2.…"; null plus a SEAL_KEY_NOT_CONFIGURED note when this deployment has no seal key) and meta.seal {algorithm, entries, expires_at, restore_bound, max_restores}. Errors: INPUT_TOO_LARGE, INVALID_PATTERN, INVALID_ARGUMENT, SEALED_MAP_INVALID, SEALED_MAP_EXPIRED, SEAL_KEY_NOT_CONFIGURED, RESTORE_KEY_REQUIRED / RESTORE_KEY_MISMATCH (priorSealedMap bound to another restore key). BEHAVIOR: Placeholder ids are random on every call unless you pass priorSealedMap; "hash" is random per call unless a hash key is set. The sealed_map is bound to the restore key header of this request (X-FQ-PII-Restore-Key, set by the operator in the client connection); without one, pii_restore_text reports counts only. Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, result	No	Yes	Yes	No
`pii_restore_text`WHAT: Fortress Shield (agent I/O PII protection). Put the original values back into texts (typically an LLM answer) that contain placeholders such as [EMAIL_k7q2m9xp4a], by opening meta.sealed_map from pii_redact_text on this Worker (or a legacy clear-text placeholder map). Numeric JSON sentinels are restored only in the redacted document they came from, matched by those bytes in any order. A different document is not rewritten. Slots for a document you did not pass are reported as JSON_NUMBER_DOC_MISMATCH. schema_range_preserved is false. WHEN: After an LLM or third party answered a prompt you sanitized with pii_redact_text (redactionStyle "placeholder"), right before showing the answer to the user. WHEN NOT: To redact (pii_redact_text) or find PII (pii_scan_text). Masked and hashed values cannot be restored; only placeholder style is reversible. COST: Free; no token. RETURNS: One "restored_document" row per text with restored, output_text, replacements, fuzzy_restored, unknown_placeholders and near_miss_placeholders. meta.restore_gate is RESTORE_KEY_OK, or RESTORE_KEY_REQUIRED / RESTORE_KEY_MISMATCH / RESTORE_LIMIT_REACHED, in which case nothing is substituted: restored is false, replacements 0, output_text is the input unchanged and sealed_replacements_withheld only counts them. restored is true only when at least one placeholder was actually replaced. Every row carries map_source ("sealed" \| "plaintext"), verified (true only for an authenticated sealed map) and exact (no fuzzy, unknown or near-miss placeholders); meta.verification and meta.audit (counts) summarise them. A clear-text placeholderMap alone is refused on deployments with a seal key (meta.restore_gate SEALED_MAP_REQUIRED, nothing substituted, plaintext_replacements_refused counts). Further gate codes (counts only): TENANT_MISMATCH (map bound to another tenantId), USER_ONLY_RESTORE (restoreAudience "user" without the X-FQ-PII-User-Present header), APPS_RESTORE_REQUIRED (operator requires a user-facing	WHAT: Fortress Shield (agent I/O PII protection). Put the original values back into texts (typically an LLM answer) that contain placeholders such as [EMAIL_k7q2m9xp4a], by opening meta.sealed_map from pii_redact_text on this Worker (or a legacy clear-text placeholder map). Numeric JSON sentinels are restored only in the redacted document they came from, matched by those bytes in any order. A different document is not rewritten. Slots for a document you did not pass are reported as JSON_NUMBER_DOC_MISMATCH. schema_range_preserved is false. WHEN: After an LLM or third party answered a prompt you sanitized with pii_redact_text (redactionStyle "placeholder"), right before showing the answer to the user. WHEN NOT: To redact (pii_redact_text) or find PII (pii_scan_text). Masked and hashed values cannot be restored; only placeholder style is reversible. COST: Free; no token. RETURNS: One "restored_document" row per text with restored, output_text, replacements, fuzzy_restored, unknown_placeholders and near_miss_placeholders. meta.restore_gate is RESTORE_KEY_OK, or RESTORE_KEY_REQUIRED / RESTORE_KEY_MISMATCH / RESTORE_LIMIT_REACHED, in which case nothing is substituted: restored is false, replacements 0, output_text is the input unchanged and sealed_replacements_withheld only counts them. restored is true only when at least one placeholder was actually replaced. Every row carries map_source ("sealed" \| "plaintext"), verified (true only for an authenticated sealed map) and exact (no fuzzy, unknown or near-miss placeholders); meta.verification and meta.audit (counts) summarise them. A clear-text placeholderMap alone is refused on deployments with a seal key (meta.restore_gate SEALED_MAP_REQUIRED, nothing substituted, plaintext_replacements_refused counts). Further gate codes (counts only): TENANT_MISMATCH (map bound to another tenantId), USER_ONLY_RESTORE (restoreAudience "user" without the X-FQ-PII-User-Present header), APPS_RESTORE_REQUIRED (operator requires a user-facing	No	Yes	Yes	No
`pii_scan_text`WHAT: Fortress Shield (agent I/O PII protection). Detect PII (emails incl. "jane [at] acme [dot] com" and "jane at acme dot com" forms, phones, US SSNs/ITINs, Luhn-valid cards, mod-97 IBANs, UK NINOs, IPv4 and full or compressed IPv6, MAC addresses, labelled dates of birth / passports / driver's licences / MRNs / health-plan ids / ABA routing numbers, Canadian SIN, NPI/DEA/MBI, VIN, Bitcoin/Ethereum wallets, ES DNI/NIE, IT codice fiscale, FR NIR, IN Aadhaar/PAN, ZIP/postcodes in a residence or ZIP context) and credential-shaped strings (common provider token formats, signed web tokens, PEM key blocks incl. a header without its END line, user:pass in URLs, key=value assignments; full list from pii_list_detectors) in text, plus your own customDetectors. Text is normalized first (NFKC, zero-width characters removed, Cyrillic/Greek look-alike letters folded), so hidden characters do not split a match. Detection only: matches are masked in the output and nothing is sent anywhere. WHEN: Before sending prompts, tickets, logs or files to an LLM or third party; to audit text for leaked credentials. Findings are paged across all documents. WHEN NOT: To get sanitized text use pii_redact_text. For unlabelled person names (NER), or to fetch PDFs and remote documents, use pii_guard_documents (paid). http(s) URLs in text you already have are detected here for free. Not for images (no OCR). COST: Free. Regex and validators on this Worker; no APIFY_TOKEN. RETURNS: Paged findings across all documents, each with a masked preview and, when a label raised it, context; raw values are never returned. meta.documents[] has context_lowered (matches kept at low confidence because of a negative context word), context_suppressed (matches left out with contextMode "drop") and typed_placeholders (placeholder-shaped text such as "[EMAIL_1]" already in the input), below_threshold and context_report (which context word lowered or skipped which type; no values). JSON input: findings carry json_path.	WHAT: Fortress Shield (agent I/O PII protection). Detect PII (emails incl. "jane [at] acme [dot] com" and "jane at acme dot com" forms, phones, US SSNs/ITINs, Luhn-valid cards, mod-97 IBANs, UK NINOs, IPv4 and full or compressed IPv6, MAC addresses, labelled dates of birth / passports / driver's licences / MRNs / health-plan ids / ABA routing numbers, Canadian SIN, NPI/DEA/MBI, VIN, Bitcoin/Ethereum wallets, ES DNI/NIE, IT codice fiscale, FR NIR, IN Aadhaar/PAN, ZIP/postcodes in a residence or ZIP context) and credential-shaped strings (common provider token formats, signed web tokens, PEM key blocks incl. a header without its END line, user:pass in URLs, key=value assignments; full list from pii_list_detectors) in text, plus your own customDetectors. Text is normalized first (NFKC, zero-width characters removed, Cyrillic/Greek look-alike letters folded), so hidden characters do not split a match. Detection only: matches are masked in the output and nothing is sent anywhere. WHEN: Before sending prompts, tickets, logs or files to an LLM or third party; to audit text for leaked credentials. Findings are paged across all documents. WHEN NOT: To get sanitized text use pii_redact_text. For unlabelled person names (NER), or to fetch PDFs and remote documents, use pii_guard_documents (paid). http(s) URLs in text you already have are detected here for free. Not for images (no OCR). COST: Free. Regex and validators on this Worker; no APIFY_TOKEN. RETURNS: Paged findings across all documents, each with a masked preview and, when a label raised it, context; raw values are never returned. meta.documents[] has context_lowered (matches kept at low confidence because of a negative context word), context_suppressed (matches left out with contextMode "drop") and typed_placeholders (placeholder-shaped text such as "[EMAIL_1]" already in the input), below_threshold and context_report (which context word lowered or skipped which type; no values). JSON input: findings carry json_path.	No	Yes	Yes	No
`sanctions_list_sources`WHAT: Static list of the official sanctions lists sanctions_screen_names checks (id, name, authority, download URL), the score scale and the legal disclaimer. WHEN: To choose the lists parameter, cite sources in a report, or explain coverage before paying. WHEN NOT: To screen a name (sanctions_screen_names, paid). It does not download lists or report freshness. COST: Free; no token. RETURNS: One static object, including the disclaimer to show with screening results. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call; static catalog compiled into this Worker, instant. No rate limits. PARAMETERS: None: call with an empty object {}; the result is static and cannot be filtered. Its output feeds sanctions_screen_names: each sources[].id (OFAC_SDN, OFAC_CONS, EU, UK, UN) is a valid value for its lists parameter, and score_scale explains how its minScore threshold is applied. EXAMPLE: {} -> {"sources":[{"id":"OFAC_SDN","authority":"US Treasury OFAC",...},...]}	WHAT: Static list of the official sanctions lists sanctions_screen_names checks (id, name, authority, download URL), the score scale and the legal disclaimer. WHEN: To choose the lists parameter, cite sources in a report, or explain coverage before paying. WHEN NOT: To screen a name (sanctions_screen_names, paid). It does not download lists or report freshness. COST: Free; no token. RETURNS: One static object, including the disclaimer to show with screening results. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs, results, or an Apify token. No further network call; static catalog compiled into this Worker, instant. No rate limits. PARAMETERS: None: call with an empty object {}; the result is static and cannot be filtered. Its output feeds sanctions_screen_names: each sources[].id (OFAC_SDN, OFAC_CONS, EU, UK, UN) is a valid value for its lists parameter, and score_scale explains how its minScore threshold is applied. EXAMPLE: {} -> {"sources":[{"id":"OFAC_SDN","authority":"US Treasury OFAC",...},...]}	No	Yes	Yes	No
`sanctions_screen_names`WHAT: Runs the Fairquery Apify Actor sanctions-watchlist-screener: fuzzy-match people/organisations against OFAC SDN, OFAC Consolidated, EU, UK and UN lists from the official sources (re-downloaded when the cached copy in your Apify account is older than 6 h; every row reports each list's publication date); optional country/DOB filters. WHEN: KYC/KYB onboarding, vendor/counterparty checks, bulk re-screening. Put all names in ONE call (each call is one run with its own start fee; list loading takes ~2-5 s from the cache, or 10-40 s, up to ~60 s, when lists are re-downloaded). This Worker waits 20 s, so a re-download that runs longer returns APIFY_TIMEOUT. WHEN NOT: PEP/adverse media, certified compliance decisions. For coverage info use free sanctions_list_sources. Leads that also have an email to validate: trust_screen_lead (one merged decision). COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $3.00 per 1,000 names + $7.00 per 1,000 runs. 200 names in one call ~ $0.61. RETURNS: Paged "screening" rows (status potential_match \| no_match, matches[] best first, lists_unavailable) or "error" rows. Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. Not a certified screening service. Automated fuzzy matching against public lists; false positives and misses are possible. Review every potential match manually and consult official sources/legal counsel before acting. BEHAVIOR: Results are stable for a given list snapshot. Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor runs in your account. Up to 10,000 names. A list re-download can outlast the 20 s wait. PARAMETERS: names and/or queries: at least one non-empty (the schema marks both optional; neither -> INPUT_EMPTY, not billed). Both may be combined; every entry is bill	WHAT: Runs the Fairquery Apify Actor sanctions-watchlist-screener: fuzzy-match people/organisations against OFAC SDN, OFAC Consolidated, EU, UK and UN lists from the official sources (re-downloaded when the cached copy in your Apify account is older than 6 h; every row reports each list's publication date); optional country/DOB filters. WHEN: KYC/KYB onboarding, vendor/counterparty checks, bulk re-screening. Put all names in ONE call (each call is one run with its own start fee; list loading takes ~2-5 s from the cache, or 10-40 s, up to ~60 s, when lists are re-downloaded). This Worker waits 20 s, so a re-download that runs longer returns APIFY_TIMEOUT. WHEN NOT: PEP/adverse media, certified compliance decisions. For coverage info use free sanctions_list_sources. Leads that also have an email to validate: trust_screen_lead (one merged decision). COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $3.00 per 1,000 names + $7.00 per 1,000 runs. 200 names in one call ~ $0.61. RETURNS: Paged "screening" rows (status potential_match \| no_match, matches[] best first, lists_unavailable) or "error" rows. Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT. Not a certified screening service. Automated fuzzy matching against public lists; false positives and misses are possible. Review every potential match manually and consult official sources/legal counsel before acting. BEHAVIOR: Results are stable for a given list snapshot. Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. The Actor runs in your account. Up to 10,000 names. A list re-download can outlast the 20 s wait. PARAMETERS: names and/or queries: at least one non-empty (the schema marks both optional; neither -> INPUT_EMPTY, not billed). Both may be combined; every entry is bill	No	Yes	Yes	Yes
`trust_screen_lead`WHAT: One call per batch of leads/counterparties: runs email_validate_deliverability on their emails and sanctions_screen_names on their person/company names IN PARALLEL, then merges results per lead with an overall decision: block (invalid email or sanctions potential_match), review (risky email), pass. WHEN: Onboarding customers/vendors, qualifying inbound leads, CRM hygiene where both email quality and sanctions exposure matter. WHEN NOT: Email only -> email_validate_deliverability; names only -> sanctions_screen_names (same per-item prices, no merge step). Free pre-filter first: email_check_syntax. Use this tool only when a lead needs both checks and one decision. COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.79 per 1,000 leads with email + $3.00 per 1,000 leads with name (= $3.79 per 1,000 full leads) + $7.00 per 1,000 calls for the sanctions run. 100 full leads ~ $0.39. RETURNS: Paged "lead" rows (decision pass \| review \| block with reasons[]; sanctions_matches holds the top 3); meta.summary counts by decision. Partial failure: the affected check shows "unavailable" and meta.errors lists codes. Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING. BEHAVIOR: No email is sent. Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. Runs the email and sanctions Apify Actors in parallel (2 runs per call) in your account. Sanctions lists come from a cache at most 6 h old, or are downloaded; a download can outlast the 20 s wait. PARAMETERS: leads: each record needs email and/or name (if no lead has either -> INPUT_EMPTY, nothing billed); a lead with only an email skips sanctions (sanctions_status "not_checked") and one with only a name skips email (email_verdict "not_checked"), so a lead is billed for each check it gets (prices under COST), plus the per-call sanctions run fee when any lead has a name. Identic	WHAT: One call per batch of leads/counterparties: runs email_validate_deliverability on their emails and sanctions_screen_names on their person/company names IN PARALLEL, then merges results per lead with an overall decision: block (invalid email or sanctions potential_match), review (risky email), pass. WHEN: Onboarding customers/vendors, qualifying inbound leads, CRM hygiene where both email quality and sanctions exposure matter. WHEN NOT: Email only -> email_validate_deliverability; names only -> sanctions_screen_names (same per-item prices, no merge step). Free pre-filter first: email_check_syntax. Use this tool only when a lead needs both checks and one decision. COST: Paid, billed to YOUR Apify account via your APIFY_TOKEN: $0.79 per 1,000 leads with email + $3.00 per 1,000 leads with name (= $3.79 per 1,000 full leads) + $7.00 per 1,000 calls for the sanctions run. 100 full leads ~ $0.39. RETURNS: Paged "lead" rows (decision pass \| review \| block with reasons[]; sanctions_matches holds the top 3); meta.summary counts by decision. Partial failure: the affected check shows "unavailable" and meta.errors lists codes. Tool errors: INPUT_EMPTY, APIFY_TOKEN_MISSING. BEHAVIOR: No email is sent. Called from this Fairquery-hosted Worker, which forwards your input and Apify token to Apify and waits 20 s (APIFY_TIMEOUT if the run has not finished). This Worker's code is designed not to store them. Runs the email and sanctions Apify Actors in parallel (2 runs per call) in your account. Sanctions lists come from a cache at most 6 h old, or are downloaded; a download can outlast the 20 s wait. PARAMETERS: leads: each record needs email and/or name (if no lead has either -> INPUT_EMPTY, nothing billed); a lead with only an email skips sanctions (sanctions_status "not_checked") and one with only a name skips email (email_verdict "not_checked"), so a lead is billed for each check it gets (prices under COST), plus the per-call sanctions run fee when any lead has a name. Identic	No	Yes	Yes	Yes

Details

Registry status: Active
Published: Oct 26, 2026
Updated: Oct 26, 2026
Website: https://getfairquery.com/posts/give-ai-agent-trust-safety-tools-mcp-server/⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing