Is BuildPulse MCP server safe?

Yes, with the usual care.

A87/100grade A

Passed every safety check we run. Maintained, authenticated, reachable, clean scan.

No critical or high findings in the latest scan.

How BuildPulse compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 87/100; higher than 73% of 1,119 Developer tools servers
Uptime: 100%; of our recent checks; the typical remote Developer tools server answers 100%

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

2 medium

Code scan3 source files scanned15/25
Live reliabilityremote reachable in 502ms (auth required)20/20
–Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
Auth qualityOAuth resource metadata advertised on 40115/15
Maintenancelast push 13 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

mediumnpm install lifecycle script presentinstall.script

package.json: … "README.md" ], "scripts": { "postinstall": "node ./lib/install.js" }, "engines…

Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

RepoPilot
Local, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.
not reviewed
Growing
A
Suvadu
Local shell history and AI agent sessions over MCP: search commands, failures, risk and git changes
not reviewed
Growing
A
Mergetrain
Queue parallel-agent worktree branches, test together, serialize and recover Git pushes.
not reviewed
Growing
A