MCP server
Brave Search
An archived reference server that should be replaced by current built-in search or a reviewed official integration.
Not made by the vendor. Read what it does before you run it.
What it can access
Uses a Brave API key and sends each search query to Brave.
Security note
The old reference server is archived. Do not make it a workshop dependency. Prefer built-in web search or Brave's current official API integration, and never search using a protected person's exact identity or location.
Do you need it?
Not this implementation. Most participants should use a current built-in web-search feature and inspect sources directly.
Capability and permissions
The legacy server sent search queries to Brave Search API using an API key. Search terms themselves can reveal names, locations, and investigative intent.
Least-privilege setup
As of 2026-09-01, the old Model Context Protocol reference server is archived. Do not install it. A technical team that still needs Brave API access should use Brave’s current official documentation, a low-limit key, and an approved client.
Harmless success test
No test is recommended for the archived package. For a replacement, search a harmless public phrase and confirm every result is opened and checked before use.
Disable, revoke, remove
Remove the old MCP configuration and package, revoke the Brave API key, and inspect API usage for unexpected searches.
When not to connect
Do not search exact protected identities, safe-house locations, secret URLs, or combinations that identify a confidential investigation.