docs(searxng): clarify capability discovery

Author: ihor-sokoliuk

README.md

@@ -108,7 +108,7 @@ For SearXNG deployment, configuration, and troubleshooting, see
     - `language` (string, optional): Language code for suggestions (e.g., "en", "fr", "de") or "all" (default: "all")
 
 - **searxng_instance_info**
-  - Discover categories and engines aggregated from reachable configured SearXNG instances, plus defaults, locales, and plugins from the primary reachable instance. The response reports `common` values present on every reachable instance and `available` values present on at least one reachable instance.
+  - Discover categories aggregated from reachable configured SearXNG instances, optionally include engine names, and inspect defaults, locales, and plugins from the primary reachable instance. Categories—and engines when requested—report `common` values present on every reachable instance and `available` values present on at least one reachable instance.
   - Inputs:
     - `includeEngines` (boolean, optional): Include enabled engine names in the response. (default: false)
     - `includeDisabled` (boolean, optional): Include disabled engine names when `includeEngines` is true. (default: false)

docs/self-hosted-searxng.md

@@ -10,7 +10,7 @@ procedure for your packaging or orchestrator.
 
 | Concern | SearXNG | mcp-searxng | Shared boundary |
 |---|---|---|---|
-| Deployment and capabilities | Runs the metasearch service and exposes its configured formats, categories, providers, locales, and plugins. | Consumes the public search and administration APIs. | A capability must exist upstream before an MCP request can rely on it. |
+| Deployment and capabilities | Runs the metasearch service and exposes its configured formats, categories, providers, locales, and plugins. | Consumes the public `/search` and `/config` endpoints. | A capability must exist upstream before an MCP request can rely on it. |
 | Request construction | Applies server defaults and forwards supported filters to upstream providers. | Initially builds upstream search requests with `format=json`, plus caller or operator defaults. | Language, safe search, categories, and engine filters can be set at both layers. |
 | Results | Produces answers, results, suggestions, corrections, and provider error metadata. | Filters, limits, formats, deduplicates, and caches returned data. | Poor or empty output can originate upstream or from MCP-side filters, limits, or cache state. |
 | Availability | Owns its process, storage, provider connectivity, and local recovery. | Selects configured replicas and performs ordered failover or optional fan-out. | Timeouts and partial failures must be diagnosed at both layers. |