updated 2026-08-12 05:02 UTC

Buildkite MCP Server

buildkite/buildkite-mcp-server

Official MCP Server for Buildkite.

MCP Servers Go Grade D Listed MIT
25.8/100
Rank #816 of 1283
Compare Buildkite MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-11 · 1d ago
Recent change
Rank +2

Is Buildkite MCP Server safe? Buildkite MCP Server scores 25.8/100 (Grade D), ranked #816 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 85% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#393 Memory Bank MCP — 25.8 (D) → #394 KonQuest Meta Ads MCP — 25.8 (D) → #396 Notify MCP Server — 25.7 (D) → #397 Tradingview MCP — 25.7 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 243 spots (#771 → #1014)
2026-08-10
HVTrust Changed
HVTrust down 4.8pts (25.8 → 21.0)
2026-08-08
Newly Listed
First tracked at rank #1001
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Buildkite MCP Server View MCP Servers Report missing data
67.6
Activity sub-score · out of 100
#395
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
52
Forks
36
Last Push
2026-08-11
yesterday
Commits (4 wk)
125
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
7
Rank Change
=
was #816

Analysis

HVTrust Dimensions vs MCP Servers

25.8 / 100 · 50.0% confidence

Buildkite MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.2 / 25
0.8 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
4.1 / 20
1.7 below avg 5.8

Activity Inputs

67.6 / 100
StarsRepository reach
10.3 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
7.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
85%
of last 100 commits verified

Is Buildkite MCP Server safe?

Public trust evidence for Buildkite MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for Buildkite MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
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?
85% 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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

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
Listed 1HVTrust 1Rank 1
2026-08-10
Rank Moved
Rank dropped 243 spots (#771 → #1014)
2026-08-10
HVTrust Changed
HVTrust down 4.8pts (25.8 → 21.0)
2026-08-08
Newly Listed
First tracked at rank #1001
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 25.8 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON