Buildpulse Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Buildpulse Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Model Context Protocol server for the BuildPulse Platform API. Surface flaky tests, CI run history, and coverage health in Claude Desktop, Cursor, ChatGPT, Cline, Windsurf, Continue, Zed, VS Code Copilot, and any other MCP-aware AI agent.
npx -y @buildpulse/mcpOr pin globally:
npm install -g @buildpulse/mcpThe package downloads the matching native binary for your platform on first install. Supported platforms: macOS arm64/x64, Linux arm64/x64, Windows x64.
Get a BuildPulse API token at <https://buildpulse.io> → Organization Settings → API Tokens.
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"buildpulse": {
"command": "npx",
"args": ["-y", "@buildpulse/mcp"],
"env": { "BUILDPULSE_TOKEN": "your-buildpulse-api-token" }
}
}
}.cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global): same JSON shape.
Cline, Continue, Windsurf, Zed, and VS Code Copilot all read an mcpServers block in their respective config files. See the install hub for copy-paste snippets per client.
| Tool | Purpose |
|---|---|
find_flaky_tests | Search a repository's flaky test inventory; filter by tags, recency, free-text. |
get_test_history | Recent disruption events for a specific test. |
list_recent_submissions | Recent CI runs for a repository. |
get_repo_flakiness | Current flakiness % over the last 14 days. |
get_repo_coverage | Current coverage % from the latest report. |
Every output that names a test or repo includes a web_url deep-link back to the BuildPulse web app — the same polish Sentry / Atlassian use in their MCP responses.
The server also ships four guided prompts (slash-pickable in clients that support them):
/triage_flaky_tests/ci_health_check/explain_test_failure/whats_red| Transport | Binary | Where it goes |
|---|---|---|
| stdio | cmd/mcp | npm → npx -y @buildpulse/mcp |
| Streamable HTTP | cmd/mcp-remote | hosted at https://mcp.buildpulse.io/mcp |
Same tool surface; same prompts; same resources. Pick whichever your client supports. The stdio path is universal; the hosted variant is the path to Claude.ai web and ChatGPT.
The server exposes two MCP resource templates so agents can pull state into context without a tool call:
buildpulse://repos/{repo}/flaky-testsbuildpulse://repos/{owner}/{name}/submissions| Variable | Required | Default |
|---|---|---|
BUILDPULSE_TOKEN | yes | — |
PLATFORM_API_URL | no | https://platform.buildpulse.io |
git clone https://github.com/BuildPulseLLC/buildpulse-mcp
cd buildpulse-mcp
go build -o ./bin/buildpulse-mcp ./cmd/mcp
go build -o ./bin/buildpulse-mcp-remote ./cmd/mcp-remoteRequires Go 1.24+.
go test ./...MIT — see LICENSE.
/docs/mcp — branded install hub with copy buttons~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.