# ExtensionDash

> Research extension listings and search results; track installs, keyword rankings, and competitors.

- name: io.github.tonic20/extensions-dashboard
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 87/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.tonic20%2Fextensions-dashboard
- tools: https://api.protogrid.dev/v1/servers/io.github.tonic20%2Fextensions-dashboard/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "extensions-dashboard": {
      "type": "http",
      "url": "https://extensiondash.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 45
- drivers: +website +reachable +uptime-100% +updated-19d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 87/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 5 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 14 of 14 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 5,240 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 37 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 14, about 5,240 tokens to load them all
- tool set hash: e4d7bed83ec1dde3986d50ebf4c41bfe
- tools last changed: 2026-10-19T08:19:16.044Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.tonic20/extensions-dashboard.svg)](https://protogrid.dev/servers/io.github.tonic20/extensions-dashboard)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `get_listing` changed (description, annotations)
  - before: 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 store and external_id. English copy, refreshed weekly from the store; refreshed_at says when. This never fetches, never answers "pending" and never starts tracking. users, rating and reviews are null when the store shows no number, which is not zero. For an extension this account tracks, get_metrics_history has its numbers over time. Shares search_catalog's 60 calls a minute per account. Without an account this answers 20 calls a day per address.
  - after: 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 store and external_id. English copy, refreshed weekly from the store; refreshed_at says when. This never fetches, never answers "pending" and never starts tracking. users, rating and reviews are null when the store shows no number, which is not zero. For an extension this account tracks, get_metrics_history has its numbers over time. Shares search_catalog's 60 calls a minute per account. Works without an account too.
- 2026-10-19 `search_catalog` changed (description, annotations)
  - before: 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 mixed. listed and known in each answer show how much of that store the catalog covers. Filter by name words (match "all" or "any"; case and punctuation are ignored, and an exact name comes first unless you sort), by one category of that store (a slug such as "productivity/developer" or "privacy-security"; an unknown one is refused with the store's list) and by inclusive ranges on users, rating, reviews, language count and description length; sort by any of those or by last update. This never fetches the store. users, rating and reviews are null when the store shows no number, which is not zero. Each row says whether it is one of yours or a competitor you track; pass its store and id to add_competitor to start tracking it. For one extension's full listing, call get_listing. Allows 60 calls a minute per account. Without an account this answers 20 calls a day per address.
  - after: 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 mixed. listed and known in each answer show how much of that store the catalog covers. Filter by name words (match "all" or "any"; case and punctuation are ignored, and an exact name comes first unless you sort), by one category of that store (a slug such as "productivity/developer" or "privacy-security"; an unknown one is refused with the store's list) and by inclusive ranges on users, rating, reviews, language count and description length; sort by any of those or by last update. This never fetches the store. users, rating and reviews are null when the store shows no number, which is not zero. Each row says whether it is one of yours or a competitor you track; pass its store and id to add_competitor to start tracking it. For one extension's full listing, call get_listing. Allows 60 calls a minute per account. Works without an account too.
- 2026-10-19 `list_scrape_runs` changed (description, annotations)
  - before: 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: the run is targeted at the search term, and a failed fetch appears here as a failure rather than as a position that never arrives. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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: the run is targeted at the search term, and a failed fetch appears here as a failure rather than as a position that never arrives. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `get_keyword_serp` changed (description, annotations)
  - before: 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 waiting, no egress spent. Use this when you want movement, or the same page the dashboard is showing. Every row carries mine and competitor flags, so "who is above me and which of them am I already tracking" is one call. Positions always travel with depth_scanned, because #1 of 9 and #1 of 50 are different results. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 waiting, no egress spent. Use this when you want movement, or the same page the dashboard is showing. Every row carries mine and competitor flags, so "who is above me and which of them am I already tracking" is one call. Positions always travel with depth_scanned, because #1 of 9 and #1 of 50 are different results. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `list_competitors` changed (description, annotations)
  - before: 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 even on days they fall out of the results. "candidates" — returned only with include_observed — is everyone else who has appeared in those searches, ranked by how often they beat you. Both are read from positions this account already recorded, not from the store: no fetch, no waiting, and each row carries the evidence behind it (how many of your terms, average position, first seen). This is the tool for deciding who is worth promoting. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 even on days they fall out of the results. "candidates" — returned only with include_observed — is everyone else who has appeared in those searches, ranked by how often they beat you. Both are read from positions this account already recorded, not from the store: no fetch, no waiting, and each row carries the evidence behind it (how many of your terms, average position, first seen). This is the tool for deciding who is worth promoting. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `remove_competitor` changed (description, annotations)
  - before: 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 either way, because they come from searches this account already runs. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 either way, because they come from searches this account already runs. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `add_competitor` changed (description, annotations)
  - before: 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 fetch: its description, install count, rating and languages start being recorded, and its position is kept even on days it falls out of the results entirely. Where it ranks has been recorded all along, from the searches this account already runs — so a competitor added today arrives with history rather than starting from zero. The description is not available when this returns. Call list_competitors with the same extension_id until this competitor's status turns from "pending" to "scraped". At most 5 competitors per store on the Free plan and 20 on Premium, because each costs a fetch of that store on every refresh. The two stores are counted separately. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 fetch: its description, install count, rating and languages start being recorded, and its position is kept even on days it falls out of the results entirely. Where it ranks has been recorded all along, from the searches this account already runs — so a competitor added today arrives with history rather than starting from zero. The description is not available when this returns. Call list_competitors with the same extension_id until this competitor's status turns from "pending" to "scraped". At most 5 competitors per store on the Free plan and 20 on Premium, because each costs a fetch of that store on every refresh. The two stores are counted separately. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `remove_keyword` changed (description, annotations)
  - before: 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 store listing: every extension's keywords are its own. A term is tracked per store language. Tracking "ad blocker" in en and again in de gives two independent keywords with their own positions. Call list_keywords for the languages an extension already tracks. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 store listing: every extension's keywords are its own. A term is tracked per store language. Tracking "ad blocker" in en and again in de gives two independent keywords with their own positions. Call list_keywords for the languages an extension already tracks. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `add_keyword` changed (description, annotations)
  - before: 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 list_keywords with the same extension_id until this term's status turns from "pending" to "scanned", or list_scrape_runs to watch the fetch itself — a fetch that fails shows up there, rather than as a position that never arrives. A term is tracked per store language. Tracking "ad blocker" in en and again in de gives two independent keywords with their own positions. Call list_keywords for the languages an extension already tracks. An extension tracks at most 10 keywords on the Free plan and 50 on Premium, counted per language: "ad blocker" in en and de is two. Past that this returns a limit error and remove_keyword has to free a slot first. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 list_keywords with the same extension_id until this term's status turns from "pending" to "scanned", or list_scrape_runs to watch the fetch itself — a fetch that fails shows up there, rather than as a position that never arrives. A term is tracked per store language. Tracking "ad blocker" in en and again in de gives two independent keywords with their own positions. Call list_keywords for the languages an extension already tracks. An extension tracks at most 10 keywords on the Free plan and 50 on Premium, counted per language: "ad blocker" in en and de is two. Past that this returns a limit error and remove_keyword has to free a slot first. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.
- 2026-10-19 `get_keyword_ranks` changed (description, annotations)
  - before: 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 and #1 of 50 are different results. A null position means we searched that deep and this extension was not in the results. A term tracked in more than one store language comes back as one series per language — the same term is a different SERP in each. Needs an ExtensionDash account: sign up at https://extensiondash.com/signup and reconnect using the URL on your /profile page.
  - after: 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 and #1 of 50 are different results. A null position means we searched that deep and this extension was not in the results. A term tracked in more than one store language comes back as one series per language — the same term is a different SERP in each. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

Full history: https://api.protogrid.dev/v1/servers/io.github.tonic20%2Fextensions-dashboard/changes

## Remotes

- https://extensiondash.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (14)

- `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 fetch: its description,
install count, rating and languages start being recorded, and its
position is kept even on days it falls out of the results entirely.
Where it ranks has been recorded all along, from the searches this
account already runs — so a competitor added today arrives with
history rather than starting from zero.

The description is not available when this returns. Call
list_competitors with the same extension_id until this competitor's
status turns from "pending" to "scraped".

At most 5 competitors per store on the Free
plan and 20 on Premium, because each costs a
fetch of that store on every refresh. The two stores are counted separately.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 list_keywords with
the same extension_id until this term's status turns from "pending" to
"scanned", or list_scrape_runs to watch the fetch itself — a fetch that
fails shows up there, rather than as a position that never arrives.

A term is tracked per store language. Tracking "ad blocker" in en and
again in de gives two independent keywords with their own positions.
Call list_keywords for the languages an extension already tracks.

An extension tracks at most 10 keywords on the
Free plan and 50 on Premium, counted per
language: "ad blocker" in en and de is two. Past that this returns a limit
error and remove_keyword has to free a slot first.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `get_extension`: One extension in full: every store listing's latest numbers plus its
tracked keywords and their current positions.

locales lists every store language this extension tracks, with a
keyword count each, so the keywords can be worked a language at a time.

Use get_metrics_history or get_keyword_ranks for movement over time.

This is the tracked view, built from what we have recorded. For an
extension this account does not track, use get_listing instead.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 and
#1 of 50 are different results. A null position means we searched that
deep and this extension was not in the results.

A term tracked in more than one store language comes back as one series
per language — the same term is a different SERP in each.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 waiting,
no egress spent. Use this when you want movement, or the same page the
dashboard is showing.

Every row carries mine and competitor flags, so "who is above me and
which of them am I already tracking" is one call. Positions always
travel with depth_scanned, because #1 of 9 and #1 of 50 are different
results.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 store and external_id.

English copy, refreshed weekly from the store; refreshed_at says when. This never fetches,
never answers "pending" and never starts tracking. users, rating and reviews are null when
the store shows no number, which is not zero. For an extension this account tracks,
get_metrics_history has its numbers over time. Shares search_catalog's
60 calls a minute per account.

Works without an account too.

- `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 days filter both.

A map holds only dates actually observed; an empty map means no
measurement in range, never zero. If users_rounded_in_range is true
the store published rounded counts somewhere in the window, so small
movements there may be rounding.

Competitors are captured every few days rather than daily, and not on
a fixed schedule, so compare a rival against "listings" on dates
present in both, never by position in the map. Join a competitor
entry back to list_competitors on (store, external_id); name is a
label, not an identifier.

include_competitors adds every roster competitor's history.
competitors narrows that to specific (store, external_id) pairs and
implies include_competitors; a pair not on the roster fails the whole
call rather than silently dropping it.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 even on days they fall out of
the results. "candidates" — returned only with include_observed —
is everyone else who has appeared in those searches, ranked by how
often they beat you.

Both are read from positions this account already recorded, not from
the store: no fetch, no waiting, and each row carries the evidence
behind it (how many of your terms, average position, first seen). This
is the tool for deciding who is worth promoting.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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: every tracking tool
takes an extension_id from this list.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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_scanned results and this extension was not among
them — that is a real observation, not missing data.

A "pending" row can still carry a position. Removing a keyword stops the
tracking but keeps the history, so a term tracked before and added again
arrives with its previous result already in place; captured_on says how
old that is. Poll until the status reads "scanned" to know the number
answers the current tracking.

locale is the store language the term was searched in. The same term
ranks differently under hl=de than under hl=en, so two rows sharing a
term and a store are two different results.

locales lists every store language this extension tracks, with a
keyword count each — start there to work a language at a time. It
always reports every language, including when the locale argument
narrows the rows to one.

search_volume is Google Ads' average monthly searches for the term in
the row's store language: for English, in the United States or
worldwide as the account's profile setting says (United States unless
changed), and in one country for the others (Germany for de, Spain for
es, Brazil for pt-BR, and so on).
It is web search demand, not searches inside the store, and is the same
for both stores. null means not fetched yet, Google has no data, or the
term can't be looked up (symbols such as + or %, over 80 characters or
10 words, or a store language Google Ads has no country for, such as
ru); search_volume_fetched_at says which.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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: the run is targeted
at the search term, and a failed fetch appears here as a failure rather
than as a position that never arrives.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 either way,
because they come from searches this account already runs.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 store listing: every extension's keywords are its own.

A term is tracked per store language. Tracking "ad blocker" in en and
again in de gives two independent keywords with their own positions.
Call list_keywords for the languages an extension already tracks.

Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

- `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 mixed. listed and known in
each answer show how much of that store the catalog covers.

Filter by name words (match "all" or "any"; case and punctuation are ignored, and an exact
name comes first unless you sort), by one category of that store (a slug such as
"productivity/developer" or "privacy-security"; an unknown one is refused with the store's
list) and by inclusive ranges on users, rating, reviews, language count and description
length; sort by any of those or by last update. This never fetches the store. users,
rating and reviews are null when the store shows no number, which is not zero. Each row
says whether it is one of yours or a competitor you track; pass its store and id to
add_competitor to start tracking it. For one extension's full listing, call get_listing.

Allows 60 calls a minute per account.

Works without an account too.