Kiro Power

Latest Audit Result

Kiro Power (exa-labs/kiro-power-exa) is a config-and-docs-only Kiro power that connects to the hosted exa-mcp-server at mcp.exa.ai. The two default MCP tools (web_search_exa, web_fetch_exa) work correctly — live tool calls confirmed search returns highlights and fetch returns clean markdown. However, `web_search_advanced_exa` is declared as Primary in POWER.md and referenced throughout all steering docs, but is NOT loaded because mcp.json lacks the `tools=` query param. This means all documented filtering, summary, configurable highlights, subpage crawling, and search-type selection features are unreachable. All 8 previously identified issues remain unfixed. The Exa API changelog (April 1 2026) deprecates startCrawlDate/endCrawlDate, resolvedSearchType, and highlightScores — Kiro Power itself does not reference these, but the upstream exa-mcp-server still exposes startCrawlDate/endCrawlDate as web_search_advanced_exa params. No SDK dependency (baseline is MCP only).

Missing Features (6)

• web_search_advanced_exa declared Primary in POWER.md but not loaded — mcp.json URL (https://mcp.exa.ai/mcp?client=kiro-power) lacks the required `tools=` selector, so only web_search_exa and web_fetch_exa are available. Live tools/list confirms this; calling web_search_advanced_exa returns 'Tool not found'.
• All features exclusive to web_search_advanced_exa are unreachable: includeDomains/excludeDomains, startPublishedDate/endPublishedDate, category (explicit param), userLocation, enableSummary, configurable enableHighlights, subpages/subpageTarget, includeText/excludeText, moderation, additionalQueries, type selection (auto/fast/instant), maxAgeHours/livecrawlTimeout — despite being documented in steering/searching.md and domain pattern files.
• DEPRECATED (upstream): exa-mcp-server's web_search_advanced_exa still exposes startCrawlDate and endCrawlDate as tool input params, but the Exa API silently ignores these since April 15 2026 and will hard-remove them May 1 2026. Kiro Power steering docs do NOT reference these, so no Kiro-side fix needed, but upstream should remove them.
• Add `tools=web_search_exa,web_search_advanced_exa,web_fetch_exa` to the mcp.json URL (`https://mcp.exa.ai/mcp?client=kiro-power&tools=web_search_exa,web_search_advanced_exa,web_fetch_exa`) to enable all three declared Primary tools. Live testing confirmed this works.
• Search type selection (auto/fast/instant) is documented in POWER.md ('Exa's default search type is auto') but only the `auto` default is reachable via web_search_exa; `fast` and `instant` require the `type` param on web_search_advanced_exa, which is not loaded.
• Basic highlights work (web_search_exa sends highlights:true by default), but configurable highlights (maxCharacters, numSentences, query) and summaries require web_search_advanced_exa's enableHighlights/enableSummary params — documented in steering/searching.md but currently unreachable.