BuildPulse MCP Server

by buildpulsellc Your server? Claim it

answering

BuildPulse is answering right now. Last checked 7 min ago. 322 installs a week from npm. Last commit 5 Nov 2026.

BuildPulse for AI agents: CI runner usage, cost and savings, plus flaky tests, failures, coverage.

Installs per day peak 223 · avg 15 · +388% w/w

a month agotoday

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

807 ms

Response time

average over 24h

322

Installs / week

npm and PyPI

What the code does

We read the source, 2 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1

postinstall: node ./lib/install.js

Runs an external command npm/bin/buildpulse-mcp.js:25, [пакет] bin/buildpulse-mcp.js:25

const child = spawn(binaryPath, process.argv.slice(2), {

Builds a file path from a variable npm/lib/install.js:39, [пакет] lib/install.js:39

  const outPath = path.join(__dirname, binaryName);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add buildpulse-mcp --transport http https://mcp.buildpulse.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.buildpulse.io/mcp

~/.codex/config.toml

[mcp_servers.buildpulse-mcp]
url = "https://mcp.buildpulse.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "buildpulse-mcp": {
      "url": "https://mcp.buildpulse.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "buildpulse-mcp": {
      "type": "http",
      "url": "https://mcp.buildpulse.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.buildpulse.io/mcp	streamable-http	sign-in	878 ms	7 min ago

Alternatives to BuildPulse

same job, measured the same way

Gaffer

by gaffer

Test analytics for AI agents: test history, flaky tests, failure clusters, coverage.

71 installs/wk local only

Forge Test MCP

by vschernoff

Runs Foundry tests and builds; returns compact, structured failures to AI coding agents

122 installs/wk local only

MCP Test Runner

by lovranran

Local test execution and coverage summaries for onboarding agents.

104 installs/wk local only

Blacksmith

by grahamnotgrant

MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests.

278 installs/wk local only

Playwright Report MCP

by hubertgajewski

Run Playwright tests and surface structured results for AI agents doing test failure analysis.

246 installs/wk local only

Testing

by rog0x

Test generation, mocks, coverage analysis for AI agents

49 installs/wk local only

Code Factory

by zrk222

Read-only audit evidence for security, tests, native coverage, runtime failures and repair status.

1 373 installs/wk local only

TurnSignal for Playwright

by turnsignal

Read-only Playwright CI results for agents: new vs known failures, flaky tests, test history.

92 installs/wk local only

BuildPulse — questions

Answers built from our own checks of this server.

Why is there no tool list for BuildPulse?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is BuildPulse working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 807 ms. The bar chart above shows every period we have measured.

How do I connect BuildPulse?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to BuildPulse?

No API key is involved. BuildPulse answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is BuildPulse?

It answers our handshake in 807 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use BuildPulse?

The npm package @buildpulse/mcp was installed 322 times in the last week. Week over week that is +388%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is BuildPulse open source?

The code is open source: it is published under the MIT licence, written in Go and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.buildpulse.io, which runs on its operator's own terms.