Is Buildkite MCP Server safe to use?

Buildkite MCP Server has an HVTrust score of 57.4/100 (Grade C), ranked #779 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Buildkite MCP Server?

Buildkite MCP Server scores 57.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 56 GitHub stars and is categorized under MCP Servers.

Buildkite MCP Server

Repository

Official MCP Server for Buildkite.

MCP Servers Go Listed MIT

Is Buildkite MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10

Provenance None

Signed commits 28%

Last push yesterday

Compare Buildkite MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Buildkite MCP Server scores 57.4/100 (Grade C), ranked #779 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 28% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Buildkite MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +7.3 → 64.7 C · #309 of 778
Sign every commit28% signed today +3.6 → 61.0 C · #366 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Buildkite MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/buildkite/buildkite-mcp-server, MIT, last pushed 2026-11-09. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection4
- Signed Releases0
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies1
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 6
Published packages None

Distributed as the container image ghcr.io/buildkite/buildkite-mcp-server:0.7.0; HVTracker doesn't check that registry's source link yet.

Changes to this chain

2026-08-31 OSSF Scorecard: 5.9/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Buildkite MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Buildkite MCP Server compares in MCP Servers

#420 Cr7258 Elasticsearch MCP Server 57.5 +0.1
#421 MeiGen AI Design MCP 57.5 +0.1
#422 Buildkite MCP Server 57.4 this agent
#423 ArcGIS MCP Bridge 57.4 ±0
#424 MCP Me 57.4 ±0

Bars show each HVTrust score; the tick marks Buildkite MCP Server’s 57.4.

Where the 57.4 comes from

HVTrust dimensions vs the MCP Servers average

57.4 / 100 · 100.0% confidence

Buildkite MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.3 / 25

2.5 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.9 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

4.2 / 20

3.4 below avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-08

Rank Moved

Rank dropped 77 spots (#709 → #786)

2026-10-24

Rank Moved

Rank dropped 16 spots (#675 → #691)

2026-10-22

Rank Moved

Rank rose 37 spots (#716 → #679)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent View MCP Servers Report missing data

68.0

Activity sub-score · out of 100

#422

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-09

yesterday

Commits (4 wk)

130

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #778

Analysis

Activity Inputs

68.0 / 100

StarsRepository reach

10.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

7.5 / 20

Common questions about Buildkite MCP Server

Buildkite MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Buildkite MCP Server publish package provenance?

No published build provenance is currently detected for Buildkite MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Buildkite MCP Server have an OpenSSF Scorecard?

Buildkite MCP Server has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Buildkite MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Buildkite MCP Server use?

Buildkite MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Buildkite MCP Server's commits signed?

28% of the last 100 commits to Buildkite MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Buildkite MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Buildkite MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Buildkite MCP Server?

For maintainers

HVTrust scores Buildkite MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-08

Rank Moved

Rank dropped 77 spots (#709 → #786)

2026-10-24

Rank Moved

Rank dropped 16 spots (#675 → #691)

2026-10-22

Rank Moved

Rank rose 37 spots (#716 → #679)

2026-10-21

Rank Moved

Rank rose 27 spots (#743 → #716)

2026-10-19

Rank Moved

Rank dropped 10 spots (#726 → #736)

2026-10-13

Rank Moved

Rank rose 10 spots (#728 → #718)

2026-10-11

Rank Moved

Rank dropped 39 spots (#688 → #727)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 27 spots (#667 → #640)

2026-09-23

HVTrust Changed

HVTrust up 28.0pts (31.6 → 59.6)

2026-09-22

Newly Listed

First tracked at rank #667

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Grade Changed

Trust grade D → C

2026-09-20

Rank Moved

Rank rose 536 spots (#1161 → #625)

2026-09-20

HVTrust Changed

HVTrust up 19.6pts (40.1 → 59.7)

2026-09-19

Grade Changed

Trust grade C → D

2026-09-19

Rank Moved

Rank dropped 539 spots (#622 → #1161)

2026-09-19

HVTrust Changed

HVTrust down 19.6pts (59.7 → 40.1)

2026-09-15

Grade Changed

Trust grade D → C

2026-09-15

Rank Moved

Rank rose 535 spots (#1159 → #624)

2026-09-15

HVTrust Changed

HVTrust up 19.6pts (40.1 → 59.7)

2026-09-14

Grade Changed

Trust grade C → D

2026-09-14

Rank Moved

Rank dropped 536 spots (#623 → #1159)

2026-09-14

HVTrust Changed

HVTrust down 19.5pts (59.6 → 40.1)

2026-09-12

Rank Moved

Rank dropped 10 spots (#613 → #623)

2026-09-11

Rank Moved

Rank dropped 11 spots (#602 → #613)

2026-09-10

Grade Changed

Trust grade D → C

2026-09-10

Rank Moved

Rank rose 546 spots (#1148 → #602)

2026-09-10

HVTrust Changed

HVTrust up 19.6pts (40.1 → 59.7)

2026-09-09

Grade Changed

Trust grade C → D

2026-09-09

Rank Moved

Rank dropped 552 spots (#596 → #1148)

2026-09-09

HVTrust Changed

HVTrust down 19.6pts (59.7 → 40.1)

2026-09-07

Rank Moved

Rank dropped 37 spots (#551 → #588)

2026-09-05

Rank Moved

Rank dropped 78 spots (#465 → #543)

2026-09-04

Grade Changed

Trust grade D → C

2026-09-04

Rank Moved

Rank rose 568 spots (#1033 → #465)

2026-09-04

HVTrust Changed

HVTrust up 19.8pts (39.9 → 59.7)

2026-09-03

Grade Changed

Trust grade C → D

2026-09-03

Rank Moved

Rank dropped 601 spots (#432 → #1033)

2026-09-03

HVTrust Changed

HVTrust down 19.8pts (59.7 → 39.9)

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 489 spots (#921 → #432)

2026-09-02

HVTrust Changed

HVTrust up 19.5pts (40.2 → 59.7)

2026-09-01

Rank Moved

Rank dropped 37 spots (#884 → #921)

2026-08-31

Scorecard Added

OSSF Scorecard: 5.9/10

2026-08-31

Rank Moved

Rank rose 345 spots (#1229 → #884)

2026-08-31

HVTrust Changed

HVTrust up 20.7pts (19.5 → 40.2)

2026-08-30

Rank Moved

Rank dropped 19 spots (#1210 → #1229)

2026-08-29

Rank Moved

Rank dropped 19 spots (#1191 → #1210)

2026-08-28

Rank Moved

Rank dropped 25 spots (#1166 → #1191)

2026-08-27

Rank Moved

Rank dropped 18 spots (#1148 → #1166)

2026-08-26

Rank Moved

Rank dropped 49 spots (#1099 → #1148)

2026-08-17

Rank Moved

Rank dropped 224 spots (#853 → #1077)

2026-08-17

HVTrust Changed

HVTrust down 4.8pts (24.8 → 20.0)

2026-08-16

Rank Moved

Rank rose 205 spots (#1058 → #853)

2026-08-16

HVTrust Changed

HVTrust up 4.8pts (20.0 → 24.8)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/buildkite-mcp-server.svg)](https://hvtracker.net/agents/buildkite-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/buildkite-mcp-server"><img src="https://hvtracker.net/badge/buildkite-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Buildkite MCP Server

How Buildkite MCP Server could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Buildkite MCP Server compares in MCP Servers

Where the 57.4 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Buildkite MCP Server

AI agent surface

Maintain Buildkite MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers