@buildpulse/mcp

MCPattesteddegraded
v0.1.7io.github.BuildPulseLLCMITUpdated 10d agonpmGitHub

BuildPulse Model Context Protocol server — flaky test analytics, coverage, and CI run history as agent-callable tools.

Endpoint healthdegraded
checked 9 days ago · never seen reachable
0% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
279Downloads/wk
10d agoLast update
Needs 1 credential before it runs
  • BUILDPULSE_TOKENAPI keyrequired

    BuildPulse API token (`bp_<64-hex>`; legacy 40-hex tokens also accepted). Create one at buildpulse.io → Organization Settings → API Tokens.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.BuildPulseLLC
LicenseMIT
Version0.1.7
Sourcenpm+mcp-registry
npm@buildpulse/mcp
GitHubBuildPulseLLC/buildpulse-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · c2ef4b8
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.7 · 8d agoHow well does this scan work?
EvalsNone
IndexedSep 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source8d ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

BuildPulse Model Context Protocol server — flaky test analytics, coverage, and CI run history as agent-callable tools.

Keywords
mcpmodel-context-protocolbuildpulseciflaky-teststest-analyticsclaudecursoranthropiccoverageci-cdtest-flakinessmcp-serverai-agentwindsurfclinevscodechatgptdevtoolstestinggithub-actions
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-15 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.

Topics

Related in analytics & dashboards