Fairquery Agent Trust & Data Safety vs Vulnify
Fairquery Agent Trust & Data Safety is an MCP server published by fairquery. Marketplaces we read that list it: 1 (Official MCP Registry). Vulnify is an MCP server published by vulnify.io. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Fairquery Agent Trust & Data Safety |  Vulnify |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.2 Downloads/month (npm): 2 434 Downloads/week (npm): 2 434 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) Not marked · First seen |
Listed Version: 0.1.4 Downloads/month (npm): 1 326 Downloads/week (npm): 105 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.1.5 Downloads/month (npm): 1 326 Downloads/week (npm): 105 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Fairquery Agent Trust & Data Safety | Vulnify |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (last published figure) | 2 |
| Forks (GitHub) (differs) | 0 (last published figure) | 0 |
| Last release (differs) | 2026-10-27 (better) | 2026-10-12 (worse) |
| Where it runs | Remote server or your machine | Remote server or your machine |
| Transport (differs) | stdio, Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/fairquery/fairquery-agent-trust-mcp | github.com/vulnify/vulnify-mcp |
| Changes in the last 7 days (differs) | 4 | 1 |
| First seen (differs) | 2026-10-17 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 19 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Fairquery Agent Trust & Data Safety
PII/secret redaction, email checks, sanctions screening and OSV vulnerability lookups for AI agents.
Vulnify
Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.
How to run each
Fairquery Agent Trust & Data Safety As a local MCP server: npm package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio fairquery-agent-trust-mcp -- npx -y @fairquery/agent-trust-mcpRequires: APIFY_TOKEN (secret)
Vulnify As a remote MCP server
claude mcp add --transport http vulnify https://mcp.vulnify.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: VULNIFY_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vulnify has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Fairquery Agent Trust & Data Safety asks for
APIFY_TOKEN (secret)
Only Vulnify asks for
VULNIFY_API_KEY (secret)VULNIFY_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Fairquery Agent Trust & Data Safety · What it can do: Vulnify · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.