MCP servers observed by Lowdown
app.trysonar/sonar MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 79 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-12 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.trysonar/sonar
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.trysonar/sonar?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-12: descriptions changed
What tools does it list?
79 tools on 2026-11-18:
sonar_ad_spy_ad_analysissonar_ad_spy_adssonar_ad_spy_analyze_adsonar_ad_spy_competitorssonar_ad_spy_hide_adssonar_ad_spy_linksonar_ad_spy_open_pagesonar_ad_spy_refreshsonar_ad_spy_scansonar_ad_spy_scriptsonar_ad_spy_search_pagessonar_ad_spy_tiktok_postssonar_ad_spy_unlinksonar_ad_spy_vaultsonar_ad_spy_vault_removesonar_ad_spy_vault_savesonar_ad_spy_vault_updatesonar_add_screenshotsonar_alert_eventssonar_analyze_competitorssonar_app_aso_scoresonar_app_changessonar_app_engagementsonar_app_extract_keywordssonar_app_keywordssonar_app_lookupsonar_app_overviewsonar_app_rankingssonar_app_revenuesonar_app_reviewssonar_app_salessonar_app_searchsonar_cancel_review_replysonar_competitor_keywordssonar_competitor_landscapesonar_create_productsonar_create_screenshot_setsonar_delete_alertsonar_delete_productsonar_delete_screenshotsonar_delete_screenshot_setsonar_delete_tracked_keywordsonar_discovered_keywordssonar_dismiss_review_replysonar_draft_review_replysonar_generate_review_insightssonar_get_appsonar_get_screenshot_setsonar_keyword_metricssonar_keyword_rankingssonar_keyword_searchsonar_keyword_suggestionssonar_list_alertssonar_list_appssonar_list_productssonar_list_screenshot_setssonar_portfoliosonar_post_review_replysonar_remove_competitorsonar_review_inboxsonar_review_insightssonar_review_respondersonar_scan_competitorsonar_screenshot_devicessonar_screenshot_layout_guidesonar_set_alertsonar_set_review_respondersonar_set_screenshot_translationssonar_star_keywordsonar_top_chartssonar_track_appsonar_track_competitorsonar_track_keywordssonar_untrack_appsonar_untrack_keywordssonar_update_keyword_notesonar_update_review_replysonar_update_screenshotsonar_update_screenshot_set
MCP Registry declaration
- Registry name:
app.trysonar/sonar - Declared version: 0.7.0
- Status: active
- Declared hosts:
trysonar.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.trysonar/sonar", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.trysonar/sonar?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:app.trysonar/sonar -- npx -y @sonarapp/mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).