[Ilya Bogin (ilya-bogin-keenable)]

Adds Keenable Web Search to the partner catalog as one new file, partners/servers/keenable-mcp-server.json, in the Web category. Existing entries are unchanged.

The entry points to the hosted server at https://api.keenable.ai/mcp over Streamable HTTP. It exposes two read-only tools: search_web_pages (a query, with optional site, publication date and max_results filters) and fetch_page_content (a URL, with an optional extraction prompt). Anonymous access needs no account or API key and is rate limited. An optional X-API-Key header lifts the limits, so the entry declares no security scheme.

Tool calls send queries, requested URLs and any supplied extraction prompts to Keenable.

I work at Keenable, which operates this service.

Tested

• check-jsonschema --verbose --schemafile partners/server-schema.json partners/servers/*.json (check-jsonschema 0.38.2, Python 3.12): ok -- validation done.
• The workflow's two uniqueness steps, run unchanged: "All 115 server names are unique across JSON files" and "All 122 security scheme keys are unique across JSON files".
• npx -y @modelcontextprotocol/inspector --cli https://api.keenable.ai/mcp --transport http --method tools/list, no credentials: search_web_pages, fetch_page_content, both annotated readOnlyHint: true.
• Anonymous tools/call search_web_pages with max_results=10: 10 results, all with non-empty snippets, 417 to 601 ms over four calls. fetch_page_content on https://learn.microsoft.com/en-us/azure/api-center/overview: 8,725 characters, no error, 292 to 526 ms over two calls.
• The terms, documentation, support and icon URLs return HTTP 200. The icon is a 400x400 PNG.

Publication in the Azure portal and an end-to-end connection from API Center or Foundry are not verified.