PII/secret redaction, email checks, sanctions screening and OSV vulnerability lookups for AI agents.
One MCP server for AI agents that handle untrusted data. It covers four jobs:
Free tools need no token or account and run on your machine. Paid tools are optional. They call public Fairquery Apify Actors with your own APIFY_TOKEN, and runs are billed to your Apify account.
| Tool | Cost | What it does |
|---|---|---|
pii_list_detectors | Free (local) | Catalog of detectors, redaction styles, and pricing for every paid tool |
pii_scan_text | Free (local) | Finds PII and secrets in text. Findings are paged and show masked values only |
pii_redact_text | Free (local) | Redacts with placeholder, mask or hash style. Can return a placeholder map |
pii_guard_documents | $0.003/doc + $0.0005/finding | Adds NER names/addresses, URLs and PDFs, and restore mode |
email_check_syntax | Free (local) | Syntax, normalization, typo suggestions, disposable/role/free-provider flags |
email_validate_deliverability | $0.002/email | DNS/MX, null MX, SPF/DMARC, mail provider, verdict |
sanctions_list_sources | Free (local) | Lists covered, issuing authorities, disclaimer |
sanctions_screen_names | $0.005/name | Fuzzy screening against OFAC SDN/Consolidated, EU, UK and UN |
osv_query_packages | Free (api.osv.dev) | Vulnerable or not, plus advisory IDs, for up to 200 exact versions |
osv_get_vulnerability | Free (api.osv.dev) | Full OSV advisory records |
osv_audit_dependencies | $0.0009/package + $0.0028/vuln | Manifest/lockfile audit with severity, fixes and recommended version |
trust_screen_lead | $0.002/email + $0.005/name | Email check and sanctions screening in parallel, merged into a pass/review/block decision per lead |
Every tool description has WHAT / WHEN / WHEN NOT / COST / RETURNS / EXAMPLE sections. Outputs are paged (limit, offset, nextOffset, hasMore). Errors use named codes: APIFY_TOKEN_MISSING, APIFY_TOKEN_INVALID, APIFY_PAYMENT_REQUIRED, APIFY_ACTOR_RUN_FAILED, APIFY_TIMEOUT, INPUT_EMPTY, INPUT_TOO_LARGE, INVALID_ECOSYSTEM, OSV_FETCH_FAILED and VULN_NOT_FOUND.
Paid tools use these Apify Actors: fairquery/llm-data-guard-pii-secrets, fairquery/email-validator-mx-disposable, fairquery/sanctions-watchlist-screener and fairquery/osv-dependency-vulnerability-check.
Requires Node.js 20 or later. APIFY_TOKEN is optional and only needed for paid tools. Get one at https://console.apify.com/settings/integrations.
claude_desktop_config.json){
"mcpServers": {
"fairquery-trust": {
"command": "npx",
"args": ["-y", "github:fairquery/fairquery-agent-trust-mcp"],
"env": { "APIFY_TOKEN": "<optional-your-apify-token>" }
}
}
}
~/.cursor/mcp.json or .cursor/mcp.json){
"mcpServers": {
"fairquery-trust": {
"command": "npx",
"args": ["-y", "github:fairquery/fairquery-agent-trust-mcp"],
"env": { "APIFY_TOKEN": "<optional-your-apify-token>" }
}
}
}
.vscode/mcp.json){
"inputs": [{ "type": "promptString", "id": "apify-token", "description": "Apify token (optional, paid tools only)", "password": true }],
"servers": {
"fairquery-trust": {
"type": "stdio",
"command": "npx",
"args": ["-y", "github:fairquery/fairquery-agent-trust-mcp"],
"env": { "APIFY_TOKEN": "${input:apify-token}" }
}
}
}
git clone https://github.com/fairquery/fairquery-agent-trust-mcp && cd fairquery-agent-trust-mcp
npm ci && npm run build && node dist/index.js # stdio
node dist/index.js --http # Streamable HTTP on http://127.0.0.1:3000/mcp (PORT, HOST env)
docker build -t fairquery-trust-mcp . && docker run -i --rm -e APIFY_TOKEN fairquery-trust-mcp
npm run smoke # initialize + tools/list + guide/annotation checks, no token
npm run test:live # every free tool live, ReDoS probes, paid tools without token -> APIFY_TOKEN_MISSING
npm run test:paid # also ONE paid call per family using APIFY_TOKEN from env (costs < $0.02)
See SECURITY.md. Free tools never contact Apify or Fairquery, and the code contains no secrets.
Sanctions results come from automated fuzzy matching and are not a certified screening service. Review every potential match yourself. Email checks do not probe SMTP mailboxes.
MIT © Fairquery
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @fairquery/agent-trust-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-fairquery-fairquery-agent-trust-mcp": {
"command": "npx",
"args": [
"-y",
"@fairquery/agent-trust-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@fairquery/agent-trust-mcpnpmFairquery Agent Trust & Data Safety works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.