Comparison

Beagle Security vs io.github.buildkite/buildkite-mcp-server

Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.buildkite/buildkite-mcp-server is an MCP server published by buildkite. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-18. 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
Marketplace	Beagle Security	io.github.buildkite/buildkite-mcp-server
Docker MCP Catalog	Listed Version: sha256:4be5e4ae4369 Forks (GitHub): 0 Pulls (Docker Hub): 35 048 Stars (Docker Hub): 1 Stars (GitHub): 1 Not marked · First seen 2026-10-11	Listed Version: sha256:00e13d1742a5 Forks (GitHub): 39 Pulls (Docker Hub): 13 237 Stars (Docker Hub): 0 Stars (GitHub): 54 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 0.7.0 Forks (GitHub): 39 Stars (GitHub): 54 Not marked · First seen 2026-10-11

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

Beagle Security vs io.github.buildkite/buildkite-mcp-server
Fact	Beagle Security	io.github.buildkite/buildkite-mcp-server
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	1 (worse)	54 (better)
Pulls (Docker Hub) (differs)	35 048 (better)	13 237 (worse)
Forks (GitHub) (differs)	0 (worse)	39 (better)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/beagle-security-mcp-server)	On your machine (ghcr.io/buildkite/buildkite-mcp-server:0.7.0)
Transport	stdio	stdio
Tools it declares (differs)	17	24
Environment variables it asks for	1, secrets among them: 1	1, secrets among them: 1
Licence	MIT	MIT
Repository (differs)	github.com/beaglesecurity/beagle-security-mcp-server	github.com/buildkite/buildkite-mcp-server
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-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

Beagle Security

In its own words, on Docker MCP Catalog:

Connects with the Beagle Security backend using a user token to manage applications, run automated security tests, track vulnerabilities across environments, and gain intelligence from Application and API vulnerability data.

io.github.buildkite/buildkite-mcp-server

In its own words, on Official MCP Registry:

MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.

How to run each

Beagle Security As a local MCP server: Docker image

Claude Code

claude mcp add --env "BEAGLE_SECURITY_API_TOKEN=<YOUR_BEAGLE_SECURITY_API_TOKEN>" --transport stdio beagle-security -- docker run -i --rm -e BEAGLE_SECURITY_API_TOKEN mcp/beagle-security-mcp-server

Requires: BEAGLE_SECURITY_API_TOKEN (secret)

io.github.buildkite/buildkite-mcp-server As a local MCP server: Docker image

Claude Code

claude mcp add --env "BUILDKITE_API_TOKEN=<YOUR_BUILDKITE_API_TOKEN>" --transport stdio buildkite-mcp-server -- docker run -i --rm -e BUILDKITE_API_TOKEN run BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0 ghcr.io/buildkite/buildkite-mcp-server:0.7.0

Requires: BUILDKITE_API_TOKEN (secret)

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

Tools each declares

Only Beagle Security declares

beagle_create_application
beagle_create_project
beagle_delete_application
beagle_delete_project
beagle_get_application
beagle_get_domain_signature
beagle_get_test_result
beagle_get_test_status
beagle_list_applications
beagle_list_projects
beagle_list_running_tests
beagle_list_test_sessions

Show the remaining 5

beagle_modify_application
beagle_modify_project
beagle_start_test
beagle_stop_test
beagle_verify_domain

Only io.github.buildkite/buildkite-mcp-server declares

access_token
create_build
create_pipeline
current_user
get_artifact
get_build
get_build_test_engine_runs
get_cluster
get_cluster_queue
get_failed_executions
get_job_logs
get_jobs

Show the remaining 12

get_pipeline
get_test
get_test_run
list_annotations
list_artifacts
list_builds
list_cluster_queues
list_clusters
list_pipelines
list_test_runs
update_pipeline
user_token_organization

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Beagle Security asks for

BEAGLE_SECURITY_API_TOKEN (secret)

Only io.github.buildkite/buildkite-mcp-server asks for

BUILDKITE_API_TOKEN (secret)

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

What it can do: Beagle Security · What it can do: io.github.buildkite/buildkite-mcp-server · 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 2026-10-18. We publish no contact details for plugin publishers.