updates details for brave search (#99)

* updates details for brave search

* resolves server-tool enumeration

Docker's mcp-registry/internal/mcp/client.go file pulls values from the env.example key when standing up the server, prior to requesting the tool list. The mcp-registry expects stdio to be the transport whereon tools are listed, but the "http" example in server.yaml causes the MCP Server to launch with an HTTP Transport, thus breaking the flow.

Author: jonathansampson

servers/brave/server.yaml

@@ -7,15 +7,33 @@ meta:
     - brave
     - search
 about:
-  title: Brave Search (Archived)
-  description: Web and local search using Brave's Search API
+  title: Brave Search
+  description: Search the Web for pages, images, news, videos, and more using the Brave Search API.
   icon: https://avatars.githubusercontent.com/u/12301619?s=200&v=4
 source:
-  project: https://github.com/modelcontextprotocol/servers
-  branch: 2025.4.24
-  dockerfile: src/brave-search/Dockerfile
+  project: https://github.com/brave/brave-search-mcp-server
 config:
+  description: Configure the Brave Search API connection
   secrets:
     - name: brave.api_key
       env: BRAVE_API_KEY
       example: YOUR_API_KEY_HERE
+  env:
+    - name: BRAVE_MCP_TRANSPORT
+      example: stdio
+      value: '{{brave.mcp_transport}}'
+    - name: BRAVE_MCP_PORT
+      example: "8080"
+      value: '{{brave.mcp_port}}'
+    - name: BRAVE_MCP_HOST
+      example: 0.0.0.0
+      value: '{{brave.mcp_host}}'
+  parameters:
+    type: object
+    properties:
+      mcp_transport:
+        type: string
+      mcp_port:
+        type: string
+      mcp_host:
+        type: string