Appdex MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Appdex revenue and download estimates: Do verified, calibrated and modeled labels stay attached to figures instead of collapsing into precise-looking facts?

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

Best fit

Access Appdex data/services from an MCP client.

What we know

The Radar identity confirms the npm package `appdex-mcp`, but this research pass did not recover enough first-party documentation to safely state its exact product scope, authentication, data model or write actions.

Maintenance / activity evidence

appdex-mcp 1.1.2 published 2026-07-27T11:40:27.361Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Unknown. Complete write authority is not verified.
Authentication not yet verified.
Unknown.

Insufficient first-party evidence.

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

All limitations / Review context

Do verified, calibrated and modeled labels stay attached to figures instead of collapsing into precise-looking facts?

The bounded review of the publisher's documented Appdex revenue and download estimates 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.

Insufficient first-party evidence.
Unknown.
Complete write authority is not verified.
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.
official docs/repository
tool inventory
auth
data handling
write actions
Exact capabilities/auth/repository/retention/write surface unresolved.
Do not infer mobile/app analytics functionality from the package name alone.

Original activity observations

appdex-mcp 1.1.2 published 2026-07-27T11:40:27.361Z

Technical identity

npm/appdex-mcp

Exact implementation source: https://www.npmjs.com/package/appdex-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:appdex-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 ↗
appdex-mcp
Recorded package identity, distribution or download evidence.
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.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Official mcpServers JSON and required APPDEX_API_KEY; app-intelligence service plan applies
Publisher page contradictory: install section explicitly says keyless 2/day, config table says required. V2 captures discrepancy instead of asserting required.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Official mcpServers JSON and required APPDEX_API_KEY; app-intelligence service plan applies | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx -y appdex-mcp
Configure / authenticate
MCP100 setup guide
Use official mcpServers config: npx -y appdex-mcp; optionally APPDEX_API_KEY. Publisher says free keyless 2 requests/day and key 5/day, though Configuration table inconsistently calls key required. Treat keyless mode as limited and verify by read-only call. Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `appdex-mcp`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove appdex-mcp

Official Documentation & Sources

What it does

The Radar identity confirms the npm package `appdex-mcp`, but this research pass did not recover enough first-party documentation to safely state its exact product scope, authentication, data model or write actions.

Capability: Data & Databases
Resource type: MCP Server
Industry: Software & Technology
Best fit: Access Appdex data/services from an MCP client.

Representative uses

Use Appdex through MCP once configured

Limitations

Exact capabilities/auth/repository/retention/write surface unresolved.
Do not infer mobile/app analytics functionality from the package name alone.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Unknown.
Data handling: Unknown.
Cost: unknown
Risk and cautions: Insufficient first-party evidence.

Access scope and cautions

Write actions: Not verified
Risk level: moderate

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

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: Use Appdex through MCP once configured.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Unknown.

What limitations and risks should I check before use?

Insufficient first-party evidence. Exact capabilities/auth/repository/retention/write surface unresolved. Do not infer mobile/app analytics functionality from the package name alone. 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.