Chrome-Stats

com.chrome-statsPublished by chrome-stats.comOfficial publisherv1.0.0Updated Oct 28, 2026

Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Chrome-Stats gives an assistant analytics on browser extensions and mobile apps across Chrome, Edge, Firefox, Google Play and the Apple App Store.

What you can do
  • Look up extension and app analytics across Chrome, Edge, Firefox, Google Play and the Apple App Store.
  • The listing names no individual tools, so the exact queries and outputs are not documented here; expect store-listing and usage statistics rather than raw data access.
When to use it
Useful when you want an assistant to pull store analytics or compare extensions and apps across the Chrome, Edge, Firefox, Google Play and Apple App Store ecosystems while researching a market, a competitor or a product idea.
Requirements
A remote MCP endpoint at chrome-stats.com reached over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared, and no local package is installed.
Before you install
OAuth grants the server access tied to your Chrome-Stats account, so review the scopes it requests. The listing does not describe which tools exist or whether any of them write data, so confirm that before relying on it.

Installation

In SourceWeft

  1. Open Chrome-Stats in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.chrome-stats%2Fchrome-stats/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "chrome-stats": {
      "type": "http",
      "url": "https://chrome-stats.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.