Is Brave Search MCP Server safe to use?

Brave Search MCP Server has an HVTrust score of 45.6/100 (Grade D), ranked #902 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Brave Search MCP Server?

Brave Search MCP Server scores 45.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.4k GitHub stars and is categorized under MCP Servers.

Brave Search MCP Server

brave/brave-search-mcp-server

MCP Servers TypeScript Grade D Listed MIT

45.6/100

Rank #902 of 1320

Compare Brave Search 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 C · 2/5 signals

Last push

2026-09-03 · 1d ago

Recent change

Rank +10

Is Brave Search MCP Server safe? Brave Search MCP Server scores 45.6/100 (Grade D), ranked #902 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.4/10; 78% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#487 KDAN PDF — 45.7 (D) → #488 SmartBear MCP — 45.6 (D) → #490 Webcomponents MCP Server — 45.6 (D) → #491 AEC Model Bridge — 45.5 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 39 spots (#863 → #902)

2026-09-03

Rank Moved

Rank dropped 58 spots (#805 → #863)

2026-09-02

Grade Changed

Trust grade B → D

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.4/10. Tighten the weakest checks to improve public safety evidence.

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 Brave Search MCP Server View MCP Servers Report missing data

69.5

Activity sub-score · out of 100

#489

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

1.4k

Forks

200

Last Push

2026-09-03

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼39

was #863

Analysis

HVTrust Dimensions vs MCP Servers

45.6 / 100 · 67.0% confidence

Brave Search MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.9 / 25

2.3 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

2.1 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

16.7 / 20

4.5 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.6 / 20

1.3 above avg 6.3

Activity Inputs

69.5 / 100

StarsRepository reach

18.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

15.0 / 25

CommunityFork signal

10.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.4 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

78%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 4

Is Brave Search MCP Server safe?

Public trust evidence for Brave Search 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 Brave Search MCP Server publish package provenance?

No published build provenance is currently detected for Brave Search 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 Brave Search MCP Server have an OpenSSF Scorecard?

Brave Search MCP Server has an OpenSSF Scorecard score of 6.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Brave Search MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Brave Search MCP Server use?

Brave Search MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Brave Search MCP Server's commits signed?

78% of the last 100 commits to Brave Search 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

Brave Search MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Brave Search MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-12

Provider Removed

Runtime surface shrank — no longer detected: Brave Search

Maintain Brave Search MCP Server?

For maintainers

HVTrust scores Brave Search 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

2026-09-04

Rank Moved

Rank dropped 39 spots (#863 → #902)

2026-09-03

Rank Moved

Rank dropped 58 spots (#805 → #863)

2026-09-02

Grade Changed

Trust grade B → D

2026-09-02

Rank Moved

Rank dropped 633 spots (#172 → #805)

2026-09-02

HVTrust Changed

HVTrust down 25.8pts (72.1 → 46.3)

2026-08-31

Grade Changed

Trust grade D → B

2026-08-31

Rank Moved

Rank rose 541 spots (#707 → #166)

2026-08-31

HVTrust Changed

HVTrust up 26.1pts (46.1 → 72.2)

2026-08-30

Grade Changed

Trust grade B → D

2026-08-30

Rank Moved

Rank dropped 557 spots (#150 → #707)

2026-08-30

HVTrust Changed

HVTrust down 26.2pts (72.3 → 46.1)

2026-08-27

Scorecard Added

OSSF Scorecard: 6.8/10

2026-08-27

Grade Changed

Trust grade D → B

2026-08-27

Rank Moved

Rank rose 579 spots (#718 → #139)

2026-08-27

HVTrust Changed

HVTrust up 32.0pts (40.6 → 72.6)

2026-08-26

Rank Moved

Rank dropped 100 spots (#618 → #718)

2026-08-24

Rank Moved

Rank rose 241 spots (#860 → #619)

2026-08-24

HVTrust Changed

HVTrust up 16.6pts (24.1 → 40.7)

2026-08-22

Rank Moved

Rank dropped 241 spots (#622 → #863)

2026-08-22

HVTrust Changed

HVTrust down 16.5pts (40.6 → 24.1)

2026-08-20

Rank Moved

Rank rose 16 spots (#636 → #620)

2026-08-19

Rank Moved

Rank rose 241 spots (#877 → #636)

2026-08-19

HVTrust Changed

HVTrust up 16.2pts (23.9 → 40.1)

2026-08-17

Rank Moved

Rank dropped 255 spots (#625 → #880)

2026-08-17

HVTrust Changed

HVTrust down 16.6pts (40.5 → 23.9)

2026-08-16

Rank Moved

Rank dropped 14 spots (#611 → #625)

2026-08-13

Rank Moved

Rank rose 252 spots (#862 → #610)

2026-08-13

HVTrust Changed

HVTrust up 16.7pts (24.0 → 40.7)

2026-08-12

Provider Removed

Runtime surface shrank — no longer detected: Brave Search

2026-08-12

Rank Moved

Rank dropped 222 spots (#640 → #862)

2026-08-12

HVTrust Changed

HVTrust down 15.1pts (39.1 → 24.0)

2026-08-10

Rank Moved

Rank dropped 26 spots (#624 → #650)

2026-08-08

Newly Listed

First tracked at rank #621

GitHub → npm: @brave/brave-search-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/brave-search-mcp-server.svg)](https://hvtracker.net/agents/brave-search-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/brave-search-mcp-server"><img src="https://hvtracker.net/badge/brave-search-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON