Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ExtensionDash

REMOTE · EXTENSIONDASH.COM

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

+2 this week 74 Trust /100

Last scanned (12 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Recent critical change

Authorization (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5088 tokens (~318/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Nov 26 +2
    • Stability: fail → pass ▲ security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 77.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.

  • 8 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 77.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 76.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://extensiondash.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=extensiondash.com CN=YE1,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA384 512d9e54bbc39c9825711186bdf4961f803
SANs: extensiondash.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of extensiondash.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
extensiondash.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://extensiondash.com/mcp Verified 200
http (plaintext) http://extensiondash.com/mcp HTTPS enforced 301 https://extensiondash.com/mcp
MCP tools · 16 exposed · ~4,461 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_competitor ~315

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. On plan_limit_reached explain the cap and offer upgrading, or ask which competitor in that store the user wants removed. Never remove automatically or retry unchanged. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
external_idstringyesChrome's 32-letter id or the AMO slug, as a search_catalog row's id gives it.
storestringyes–

No output schema declared.

No examples provided.

add_extension ~308

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 without the user's request. Supply both URLs in one call only when they are the same product: they share one extension_id and consume one plan slot. Repeating an existing URL is a no-op, including at the cap. If one URL matches existing tracking, its missing store is attached and existing keywords are adopted. Conflicting listings are refused, never replaced or merged. Free allows 1 tracked extension; Premium allows 10. The response includes current usage and limits. A plan_limit_reached error is not retryable unchanged: explain it, offer the pricing link, or ask which existing extension the user wants removed with remove_extension. Never delete tracking automatically to free a slot. Cached metrics may be available immediately; fresh metrics run in the background. Use get_extension and list_scrape_runs to check progress; do not promise a completion time. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

NameTypeReqDescription
chrome_urlstring–HTTPS Chrome Web Store listing URL; at least one store URL is required.
firefox_urlstring–HTTPS Firefox Add-ons listing URL, optionally paired with the same product's Chrome URL.

No output schema declared.

No examples provided.

add_keyword ~371

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. Explain the limit and offer upgrading, or ask which keyword the user wants removed with remove_keyword. Never remove automatically or retry unchanged. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
localestring–Store language to search in: "en", "de", "pt-BR". Defaults to "en". The same term ranks differently in each, so this is a separate keyword, not a translation. Canonicalised before use, so "DE" and "d…
termstringyesThe search term, e.g. "json viewer". Squished and lowercased before use.

No output schema declared.

No examples provided.

get_extension ~193

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_tied = others at the same count); rank_change is the move since last week's recorded rank. 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`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.

No output schema declared.

No examples provided.

get_keyword_ranks ~352

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. Each series has a source. "store" is the store's own search. "google" is where the listing page ranks in Google: organic results only (ads and other blocks are not counted), top 50, desktop, in the keyword language's country (English: the United States). A null Google position means Google was searched 50 deep and the listing was not there. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

NameTypeReqDescription
daysinteger–How far back to look. Defaults to 30.
extension_idintegeryesFrom list_extensions.
localestring–Store language, e.g. "de". Omit for every language. Canonicalised before use, so "DE" and "de" are one keyword and "pt-br" comes back as "pt-BR".
sourcestring–Store search or Google. Omit for both.
storestring––
termstring–One term. Omit for all of them.

No output schema declared.

No examples provided.

get_keyword_serp ~250

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`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
localestring–Store language. Defaults to "en".
storestringyes–
termstringyesA term this extension tracks. From list_keywords.
windowboolean–Return only the leaders and our own neighbourhood rather than the whole page. Defaults to false.

No output schema declared.

No examples provided.

get_listing ~229

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. rank is the position by users within the store; ties share a rank (rank_tied = others at the same count); recomputed weekly on rank_on; rank_change is the move since the week before, positive = up. 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.

NameTypeReqDescription
external_idstringyesChrome's 32-letter id or the AMO slug, as a search_catalog row's id gives it.
storestringyes–

No output schema declared.

No examples provided.

get_metrics_history ~383

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`.

NameTypeReqDescription
competitorsarray–Limit competitor history to these (store, external_id) pairs from list_competitors. Implies include_competitors; an unlisted pair fails the call.
daysinteger–How far back to look. Defaults to 30.
extension_idintegeryesFrom list_extensions.
include_competitorsboolean–Also return history for this extension's promoted competitors. Defaults to false.
storestring–Filters both listings and competitors. Omit for every store.

No output schema declared.

No examples provided.

list_competitors ~223

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`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
include_observedboolean–Also return unpromoted candidates. Defaults to false.

No output schema declared.

No examples provided.

list_extensions ~134

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. Includes effective plan limits and extension usage (null caps mean unlimited). If empty, help the user choose a store listing and call add_extension when asked. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_keywords ~492

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`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
localestring–Store language, e.g. "de". Omit for every language. Canonicalised before use, so "DE" and "de" are one keyword and "pt-br" comes back as "pt-BR".

No output schema declared.

No examples provided.

list_scrape_runs ~157

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`.

NameTypeReqDescription
extension_idinteger–Narrow to one extension's listings and tracked keywords.
limitinteger–Defaults to 20.
statusstring––

No output schema declared.

No examples provided.

remove_competitor ~133

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`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
external_idstringyesFrom list_competitors.
storestringyes–

No output schema declared.

No examples provided.

remove_extension ~167

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 limit. This deletes this account's extension record, notes, keyword tracking and competitor configuration for it, across both stores. Re-adding does not restore that configuration. Shared store listings, collected metrics/rank history and other users' tracking remain. A missing or already removed id returns the same error as another account's id. Needs an ExtensionDash account: sign in from your app, e.g. `claude mcp login extensions-dashboard` or `codex mcp login extensions-dashboard`.

NameTypeReqDescription
extension_idintegeryesThe user's chosen extension_id from list_extensions.

No output schema declared.

No examples provided.

remove_keyword ~238

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`.

NameTypeReqDescription
extension_idintegeryesFrom list_extensions.
localestring–Store language to search in: "en", "de", "pt-BR". Defaults to "en". The same term ranks differently in each, so this is a separate keyword, not a translation. Canonicalised before use, so "DE" and "d…
termstringyesAs reported by list_keywords.

No output schema declared.

No examples provided.

search_catalog ~516

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. rank is the position by users within the store; ties share a rank (rank_tied = others at the same count); recomputed weekly on rank_on; rank_change is the move since the week before, positive = up. 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.

NameTypeReqDescription
categorystring–One category slug of the chosen store, as rows return it.
description_length_maxinteger––
description_length_mininteger––
dirstring–Defaults to desc. Nulls always last.
langs_maxinteger––
langs_mininteger––
limitinteger–Defaults to 25.
matchstring–Defaults to all.
pageinteger–Defaults to 1.
querystring–Name words, at most 8 words.
rating_maxnumber––
rating_minnumber––
reviews_maxinteger––
reviews_mininteger––
screenshots_maxinteger––
screenshots_mininteger––
sortstring–Defaults to users, with an exact name match first when query is given.
storestring–Defaults to chrome.
users_maxinteger––
users_mininteger––

No output schema declared.

No examples provided.

Install

How do I install the ExtensionDash MCP server?

ExtensionDash is a hosted endpoint at https://extensiondash.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · extensiondash.com

# add to Claude Code
claude mcp add --transport http tonic20-extensions-dashboard 'https://extensiondash.com/mcp'
Common questions

What is the ExtensionDash MCP server?

ExtensionDash is an MCP server listed in the public MCP registry as io.github.tonic20/extensions-dashboard. Research extension listings and search results; track installs, keyword rankings, and competitors. This page covers its hosted endpoint (https://extensiondash.com/mcp).

Is the ExtensionDash MCP server safe to use?

ExtensionDash scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ExtensionDash MCP server expose?

ExtensionDash exposes 16 tools: list_extensions, add_extension, remove_extension, get_extension, get_metrics_history, and 11 more. Their descriptions and schemas cost roughly 4,461 tokens of context every time the server is loaded.

Does the ExtensionDash MCP server require authentication?

No. We connected to ExtensionDash without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ExtensionDash MCP server still maintained?

ExtensionDash is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ExtensionDash MCP server?

VerifyMCP ran 13 checks on ExtensionDash, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.