Ext Ops Panel
Open dashboard
Comparison

Cylera vs BeVigil OSINT

Cylera is an MCP server published by Cylera. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-26. 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
MarketplaceCyleraBeVigil OSINT
Docker MCP Catalog Listed
Version: sha256:ba2c8606725b
Forks (GitHub): 1
Pulls (Docker Hub): 10 976
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

Cylera vs BeVigil OSINT
FactCyleraBeVigil OSINT
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)1 (worse)
Pulls (Docker Hub) (differs)10 976No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/cylera-mcp-server)On your machine (bevigil-mcp-server)
Transportstdiostdio
Tools it declares (differs)7Not published
Environment variables it asks for (differs)3, secrets among them: 31, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/cylera/cylera-mcp-servergithub.com/santhosh-005/bevigil-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Cylera

In its own words, on Docker MCP Catalog:

Brings context about device inventory, threats, risks and utilization powered by the Cylera Partner API into an LLM.

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

Cylera As a local MCP server: Docker image

Claude Code
claude mcp add --env "CYLERA_BASE_URL=<YOUR_CYLERA_BASE_URL>" --env "CYLERA_PASSWORD=<YOUR_CYLERA_PASSWORD>" --env "CYLERA_USERNAME=<YOUR_CYLERA_USERNAME>" --transport stdio cylera-mcp-server -- docker run -i --rm -e CYLERA_BASE_URL -e CYLERA_PASSWORD -e CYLERA_USERNAME mcp/cylera-mcp-server

Requires: CYLERA_BASE_URL (secret), CYLERA_PASSWORD (secret), CYLERA_USERNAME (secret)

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.

Tools each declares

The marketplaces of BeVigil OSINT publish no list of tools, so we do not compare tools.

Settings each asks for

Only Cylera asks for

  • CYLERA_BASE_URL (secret)
  • CYLERA_PASSWORD (secret)
  • CYLERA_USERNAME (secret)

Only BeVigil OSINT asks for

  • BEVIGIL_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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