Ext Ops Panel
Open dashboard
Comparison

Default Privacy vs BeVigil OSINT

Default Privacy is an MCP server published by privatebydefault. Marketplaces we read that list it: 1 (Official MCP Registry). BeVigil OSINT is an MCP server published by santhosh-005. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
MarketplaceDefault PrivacyBeVigil OSINT
Official MCP Registry Listed
Version: 1.8.0
No figure published
Not marked · First seen
Listed
Version: 1.1.0
Downloads/month (npm): 157
Downloads/week (npm): 19
Forks (GitHub): 0
Stars (GitHub): 1
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

Default Privacy vs BeVigil OSINT
FactDefault PrivacyBeVigil OSINT
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-17Not published
Where it runs (differs)Remote server (mcp.defaultprivacy.com)On your machine (bevigil-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/santhosh-005/bevigil-mcp-server
Changes in the last 7 days (differs)30
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

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

Default Privacy

In its own words, on Official MCP Registry:

Sourced privacy answers: how private an app is, tool picks, app swaps, de-Googling, breaches.

BeVigil OSINT

In its own words, on Official MCP Registry:

Discover mobile app attack surfaces via BeVigil OSINT — hosts, subdomains, URLs, and more.

How to run each

Default Privacy As a remote MCP server

Claude Code
claude mcp add --transport http default-privacy https://mcp.defaultprivacy.com

BeVigil OSINT As a local MCP server: npm package

Claude Code
claude mcp add --env "BEVIGIL_API_KEY=<YOUR_BEVIGIL_API_KEY>" --transport stdio bevigil -- npx -y bevigil-mcp-server

Requires: BEVIGIL_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Default Privacy has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of BeVigil OSINT nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Default Privacy publish no settings it asks for, so we do not compare settings.

What it can do: Default Privacy · What it can do: BeVigil OSINT · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built