mcp-server-brave-search

An MCP server that wraps Brave Search, exposing search capabilities to MCP-compatible agents/tools.

Evaluated Apr 04, 2026 (17d ago)

Homepage ↗ Repo ↗ Search mcp brave-search web-search agent-tools tooling retrieval

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Scores are based on limited information (no code/README provided here). Typical risks include mishandling API keys in logs/environment, insufficient request validation in an agent-exposed server, and lack of clear rate-limit/error semantics. Upstream TLS/auth strength depend on the MCP server implementation and Brave integration details, which are not verifiable from the provided content.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want agents to perform live web search via MCP rather than directly calling Brave APIs themselves.

Avoid When

You cannot provide/secure required API credentials for Brave or you require strict guarantees about logging/data retention beyond what the implementation provides.

Use Cases

• Agentic web search and retrieval of current information
• Answer augmentation with web results/snippets
• Tool-based browsing workflows inside an MCP client
• Building RAG/search pipelines that need web discovery

Not For

• Offline/static knowledge tasks with no need for web search
• Use as a compliance-grade search/browsing gateway without additional controls
• High-assurance environments without verifying upstream Brave and MCP server security posture

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Brave API key (implied by Brave Search usage)

OAuth: No Scopes: No

No README/manifests were provided here, so exact auth mechanism, environment variables, or scope semantics are inferred only at the level of “API key likely required” for Brave Search.

Pricing

Free tier: No

Requires CC: No

Pricing for Brave Search (and any hosting for the MCP server) is not provided in the supplied information.

Agent Metadata

Pagination

unknown

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Search operations may be non-idempotent only in the sense of relying on changing external results/time; do not assume stable ordering across retries.
⚠ Agents should rate their requests to avoid upstream Brave limits (rate-limit headers/behavior not provided here).
⚠ If the MCP server does not expose explicit “query parameters for pagination”, agents may need to implement their own iterative querying.

Alternatives

Direct Brave Search API integration Other MCP web-search providers (if available in your ecosystem) General-purpose browsing/search tools exposed through your agent runtime SerpAPI or other search aggregation APIs

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-brave-search.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.