Adds a disabled-by-default YAML example for public web research through CyberStrikeAI's existing External MCP HTTP loader. Users can merge the server entry into their own config and set disabled: false to opt in. Existing provider choices and default configuration are preserved.
English and Chinese guides cover setup, restart behavior, role tool keys, monitoring, third-party data handling, and troubleshooting. They also explain that stopping a connection in the UI does not replace disabled: true for keeping it off after restart.
Validation:
- Loaded the example through
config.Load, including disabled and enabled states. - Tested role selection, search and fetch through the External MCP manager, Agent mapping, Eino bridge, and ADK runner with a deterministic model fixture producing a sourced final answer.
- Checked actual discovery, search, and fetch HTTP requests for the CyberStrikeAI User-Agent and absence of authentication headers.
- Ran a live keyless search and fetch check, including the application's bounded output previews.
- Ran focused config, MCP, Agent, and Eino tests, and checked local documentation links, code fences, bilingual filenames, navigation coverage, and documented Go versions.
The optional live check needs network access and can fail when the service is unavailable or rate limited. It does not call the configured AI provider.
I work at Parallel. This contribution was prepared with AI assistance.