Connect ExtensionDash and your agent gets 16 tools, among them add_competitor, add_extension, add_keyword. It answers at https://extensiondash.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 1 October 2026; the last check, on 16 November 2026, succeeded.
Research extension listings and search results; track installs, keyword rankings, and competitors.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_competitor | Start tracking a competitor for an extension. Takes the store and id of a search_catalog row (as external_id), so a listing you just found can be promoted without looking anything up in between. Promoting a listing is what earns it a store Inputs: extension_id, store, external_id |
add_extension | Track the user's own extension from its Chrome Web Store and/or Firefox Add-ons URL. Resolve a name with search_catalog first; pass the selected result's url. Do not guess between ambiguous listings or start tracking research results withou Inputs: chrome_url, firefox_url |
add_keyword | Start tracking a search term for an extension. The term is added once per store the extension is listed in, and a rank fetch is enqueued for each store that was not already tracking it. The position is not available when this returns. Call Inputs: extension_id, term, locale |
get_extension | One extension in full: every store listing's latest numbers plus its tracked keywords and their current positions. Each listing's rank is its position by users within its store, computed from the current user count; ties share a rank (rank_ Inputs: extension_id |
get_keyword_ranks | Daily search position history for an extension's tracked keywords, one series per term per store. Every point carries the depth it was scanned to, because a position only means something against the size of the pool it came from: #1 of 9 an Inputs: extension_id, term, store, locale, source, days |
get_keyword_serp | The search page for one of an extension's tracked keywords, as this account last recorded it — who was on it, in what order, and which way each of them moved over the past week. Read from recorded history, not from the store: no fetch, no w Inputs: extension_id, store, term, locale, window |
get_listing | One extension's full listing from the catalog -- any extension, tracked by this account or not: description, users, rating, reviews, version, languages, categories, permissions and publisher. Pass the store and id of a search_catalog row as Inputs: store, external_id |
get_metrics_history | Daily-or-sparser history of an extension's numbers: user count, rating and ratings count, each as a map of ISO date to value. "listings" is this extension's own store listings; "competitors" is its roster from list_competitors. store and da Inputs: extension_id, store, days, include_competitors, competitors |
list_competitors | Who this extension competes with, measured across every keyword it tracks. Two sets. "competitors" is the roster you promoted with add_competitor: their descriptions, install counts and ratings are recorded, and their positions are kept eve Inputs: extension_id, include_observed |
list_extensions | Every extension this token's owner tracks, with each store listing's latest numbers: user count (and whether the store rounded it), the 7-day change, rating, ratings count and category rank. Start here when this connection has an account: e |
list_keywords | Every search term tracked for one extension, one row per term per store. status is "pending" until a fetch has landed since the term was tracked, and "scanned" once one has. A "scanned" row with a null position means we searched depth_scann Inputs: extension_id, locale |
list_scrape_runs | Recent scrape attempts against your own extensions, newest first, with their outcome and any error. Covers both the listing fetches and the rank fetches for the search terms they track. Use this after add_keyword to watch the rank fetch: th Inputs: status, extension_id, limit |
remove_competitor | Stop tracking a competitor for an extension. Stops the store fetches. The recorded history is kept, so adding the same competitor again later restores its charts rather than starting from zero — and its positions carry on being observed eit Inputs: extension_id, store, external_id |
remove_extension | Stop tracking one of this account's extensions, using an extension_id from list_extensions. Remove only the extension the user asked to remove; clarify ambiguous names first. Never remove an extension automatically to make room at a plan li Inputs: extension_id |
remove_keyword | Stop tracking a search term for an extension, across every store it was tracked in. Positions already recorded are kept; only the tracking stops. Other extensions tracking the same term are unaffected, including ones that track the same sto Inputs: extension_id, term, locale |
search_catalog | Search one store's catalog of extensions fetched so far, for market and niche research: store "chrome" (default) or "firefox", one per call -- Chrome users are a rounded weekly count, Firefox's an exact daily average, so the two are never m Inputs: store, category, query, match, sort, dir |
Every block below points at https://extensiondash.com/mcp. Pick your client and copy.
claude mcp add --transport http extensiondash https://extensiondash.com/mcp
{
"mcpServers": {
"extensiondash": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://extensiondash.com/mcp"]
}
}
}{
"mcpServers": {
"extensiondash": {
"url": "https://extensiondash.com/mcp"
}
}
}{
"servers": {
"extensiondash": {
"type": "http",
"url": "https://extensiondash.com/mcp"
}
}
}{
"context_servers": {
"extensiondash": {
"url": "https://extensiondash.com/mcp"
}
}
}{
"mcpServers": {
"extensiondash": {
"serverUrl": "https://extensiondash.com/mcp"
}
}
}{
"mcpServers": {
"extensiondash": {
"url": "https://extensiondash.com/mcp"
}
}
}name: ExtensionDash
version: 0.0.1
schema: v1
mcpServers:
- name: ExtensionDash
type: streamable-http
url: https://extensiondash.com/mcp{
"mcpServers": {
"extensiondash": {
"httpUrl": "https://extensiondash.com/mcp"
}
}
}{
"mcpServers": {
"extensiondash": {
"type": "http",
"url": "https://extensiondash.com/mcp"
}
}
}{
"mcpServers": {
"extensiondash": {
"url": "https://extensiondash.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fextensiondash.com%2Fmcp&type=streamable_http&id=extensiondash&name=ExtensionDash
It answered our last check on 16 November 2026 in 360 ms. Over 4 checks since 1 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
16, as returned by the server's own tools/list on 19 November 2026: add_competitor, add_extension, add_keyword, get_extension, get_keyword_ranks, get_keyword_serp, get_listing, get_metrics_history, and 8 more.
It answered our last check on 16 November 2026 in 360 ms. Over 4 checks since 1 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://extensiondash.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.tonic20. Endpoint host: extensiondash.com. ARD identifier: urn:air:io.github.tonic20:mcp:extensions-dashboard.
First indexed 1 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.