Sonar MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Sonar app-store research, keyword and review tools: Do read-only estimates remain labeled separately from authenticated ASO operations and credit-consuming requests?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

App-store intelligence, ASO research and workspace operations for iOS/Android teams.

What we know

Official Sonar MCP for app lookup/search, ASO audits, keywords, reviews, revenue estimates, workspace tracking, alerts and screenshot-set authoring.

Maintenance / activity evidence

@sonarapp/mcp 0.11.0 published 2026-10-01T16:44:27.855Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Public research plus private workspace and write operations depending on scope/plan. Writes: Track/untrack apps/competitors/keywords; Create/delete products; Update keyword notes/tracking; Create/update/delete alerts; Create/update/delete screenshot sets; Trigger AI analyses.
OAuth or API key.
Sensitive access: Private app portfolio, Sales/engagement data, Competitor strategy, Workspace notes

Can expose private business analytics and mutate ASO workspaces; use read-only keys when possible.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do read-only estimates remain labeled separately from authenticated ASO operations and credit-consuming requests?

The bounded review of the publisher's documented Sonar app-store research, keyword and review tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can expose private business analytics and mutate ASO workspaces; use read-only keys when possible.
Public research plus private workspace and write operations depending on scope/plan.
OAuth or API key.
Inputs are sent to Sonar; workspace data persists in account until deletion and request logging is used for rate limiting/abuse prevention.
Reviewed write actions: Track/untrack apps/competitors/keywords; Create/delete products; Update keyword notes/tracking; Create/update/delete alerts; Create/update/delete screenshot sets; Trigger AI analyses
Sensitive access: Private app portfolio, Sales/engagement data, Competitor strategy, Workspace notes
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Anonymous free mode is rate-limited.
Private workspace/sales features require account entitlements and sometimes App Store Connect.
Hosted mode excludes local ZIP export.
Some features require paid plan/write scope.

Original activity observations

@sonarapp/mcp 0.11.0 published 2026-10-01T16:44:27.855Z

Technical identity

npm/@sonarapp/mcp

Exact implementation source: https://www.npmjs.com/package/@sonarapp/mcp ↗
Reviewed resource type: MCP Server
Repository identity: trysonar/mcp
Package identity: npm:@sonarapp/mcp
Service endpoint: https://trysonar.app/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@sonarapp/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
trysonar/mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
trysonar.app/privacy
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Hosted OAuth route; local stdio alternative. Some write tools require paid plan and write scope.
publisher documented step or launch · Publisher instructions
claude mcp add --transport http sonar https://trysonar.app/mcp
Configure / authenticate
MCP100 setup guide
Sonar offers hosted OAuth (read/write workspace access) or local/API-key path; writes need appropriate scope and Indie+ plan. Check only list/read operations; do not add competitors or run paid AI tools.
remote_streamable_http: https://trysonar.app/mcp
Environment variables referenced by this route (respect the alternatives above): SONAR_API_KEY
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Official Sonar MCP for app lookup/search, ASO audits, keywords, reviews, revenue estimates, workspace tracking, alerts and screenshot-set authoring.

Capability: Data & Databases
Resource type: MCP Server
Industry: Media & Marketing
Best fit: App-store intelligence, ASO research and workspace operations for iOS/Android teams.

Representative uses

Search/inspect apps
Audit ASO and keywords
Analyze reviews/revenue estimates
Track apps/competitors/keywords
Use private sales/engagement data when entitled
Manage screenshot sets

Limitations

Anonymous free mode is rate-limited.
Private workspace/sales features require account entitlements and sometimes App Store Connect.
Hosted mode excludes local ZIP export.
Some features require paid plan/write scope.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth or API key.
Permissions: Public research plus private workspace and write operations depending on scope/plan.
Data handling: Inputs are sent to Sonar; workspace data persists in account until deletion and request logging is used for rate limiting/abuse prevention.
Cost: freemium
Risk and cautions: Can expose private business analytics and mutate ASO workspaces; use read-only keys when possible.

Access scope and cautions

Write actions: Track/untrack apps/competitors/keywords Create/delete products Update keyword notes/tracking Create/update/delete alerts Create/update/delete screenshot sets Trigger AI analyses
Sensitive access: Private app portfolio Sales/engagement data Competitor strategy Workspace notes
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search/inspect apps; Audit ASO and keywords; Analyze reviews/revenue estimates; Track apps/competitors/keywords; Use private sales/engagement data when entitled; Manage screenshot sets.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @sonarapp/mcp. Recorded endpoint: https://trysonar.app/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: SONAR_API_KEY (optional/free mode); SONAR_API_URL (optional). No configuration values are supplied here. Prerequisites: MCP client; Sonar account/credits for account features. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Hosted OAuth or Sonar API key.

Can it modify data or perform write operations?

Documented write actions include: Track/untrack apps/competitors/keywords; Create/delete products; Update keyword notes/tracking; Create/update/delete alerts; Create/update/delete screenshot sets; Trigger AI analyses. Recorded permission boundary: Public research plus private workspace and write operations depending on scope/plan.

What data-handling boundary should I consider?

Inputs are sent to Sonar; workspace data persists in account until deletion and request logging is used for rate limiting/abuse prevention. Recorded sensitive-access context: Private app portfolio; Sales/engagement data; Competitor strategy; Workspace notes.

What limitations and risks should I check before use?

Can expose private business analytics and mutate ASO workspaces; use read-only keys when possible. Anonymous free mode is rate-limited. Private workspace/sales features require account entitlements and sometimes App Store Connect. Hosted mode excludes local ZIP export. Some features require paid plan/write scope. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Sonar / trysonar is listed as First-party MCP in MCP100’s current evidence.