_ registry / mcp streamable-http · checked 2h ago

extensions-dashboard

https://extensiondash.com

Registry code: 2b639d4d6b73db3c

api record

Chrome Web Store and Firefox Add-ons data, for store SEO work.

Two things live here. The tracking side covers the extensions this

endpoint
https://extensiondash.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is extensions-dashboard live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is extensions-dashboard free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does extensions-dashboard have?
16 tools: list_scrape_runs, remove_extension, remove_keyword, add_extension, add_keyword, add_competitor, remove_competitor, get_listing, ….
Is extensions-dashboard safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99%

90 days 99.3%· all time 99.3%

latency
348ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 303 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • track chrome extension search ranks
  • search the chrome web store
  • get extension metrics history
  • track competitor extensions
takes → gives
text → data
tools
9 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 16 tools
1 open7 auth-required 8 never probed 8 of 16 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_catalog reads open 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "dir": {
          "enum": [
            "desc",
            "asc"
          ],
          "type": "string",
          "description": "Defaults to desc. Nulls always last."
        },
        "page": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 1,
          "description": "Defaults to 1."
        },
        "sort": {
          "enum": [
            "users",
            "rating",
            "reviews",
            "langs",
            "description_length",
            "screenshots",
            "updated",
            "added"
          ],
          "type": "string",
          "description": "Defaults to users, with an exact name match first when query is given."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Defaults to 25."
        },
        "match": {
          "enum": [
            "all",
            "any"
          ],
          "type": "string",
          "description": "Defaults to all."
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "Name words, at most 8 words."
        },
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string",
          "description": "Defaults to chrome."
        },
        "category": {
          "type": "string",
          "maxLength": 64,
          "description": "One category slug of the chosen store, as rows return it."
        },
        "langs_max": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "langs_min": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "users_max": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "users_min": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "rating_max": {
          "type": "number",
          "maximum": 5,
          "minimum": 0
        },
        "rating_min": {
          "type": "number",
          "maximum": 5,
          "minimum": 0
        },
        "reviews_max": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "reviews_min": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "screenshots_max": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "screenshots_min": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "description_length_max": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        },
        "description_length_min": {
          "type": "integer",
          "maximum": 2147483647,
          "minimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 127 lines
  • get_extension reads auth-required 19h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id"
      ],
      "properties": {
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • list_competitors reads auth-required 19h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id"
      ],
      "properties": {
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        },
        "include_observed": {
          "type": "boolean",
          "description": "Also return unpromoted candidates. Defaults to false."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_keyword_serp reads auth-required 16h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id",
        "store",
        "term"
      ],
      "properties": {
        "term": {
          "type": "string",
          "description": "A term this extension tracks. From list_keywords."
        },
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string"
        },
        "locale": {
          "type": "string",
          "description": "Store language. Defaults to \"en\"."
        },
        "window": {
          "type": "boolean",
          "description": "Return only the leaders and our own neighbourhood rather than the whole page. Defaults to false."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • list_keywords reads auth-required 16h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id"
      ],
      "properties": {
        "locale": {
          "type": "string",
          "description": "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\"."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_metrics_history reads auth-required 19h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 365,
          "minimum": 1,
          "description": "How far back to look. Defaults to 30."
        },
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string",
          "description": "Filters both listings and competitors. Omit for every store."
        },
        "competitors": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "store",
              "external_id"
            ],
            "properties": {
              "store": {
                "enum": [
                  "chrome",
                  "firefox"
                ],
                "type": "string"
              },
              "external_id": {
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "description": "Limit competitor history to these (store, external_id) pairs from list_competitors. Implies include_competitors; an unlisted pair fails the call."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        },
        "include_competitors": {
          "type": "boolean",
          "description": "Also return history for this extension's promoted competitors. Defaults to false."
        }
      },
      "additionalProperties": false
    }
    arguments 56 lines
  • get_keyword_ranks reads auth-required 16h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 365,
          "minimum": 1,
          "description": "How far back to look. Defaults to 30."
        },
        "term": {
          "type": "string",
          "description": "One term. Omit for all of them."
        },
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string"
        },
        "locale": {
          "type": "string",
          "description": "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\"."
        },
        "source": {
          "enum": [
            "store",
            "google"
          ],
          "type": "string",
          "description": "Store search or Google. Omit for both."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • list_extensions reads auth-required 13h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_scrape_runs reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Defaults to 20."
        },
        "status": {
          "enum": [
            "running",
            "success",
            "failure"
          ],
          "type": "string"
        },
        "extension_id": {
          "type": "integer",
          "description": "Narrow to one extension's listings and tracked keywords."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • remove_extension unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id"
      ],
      "properties": {
        "extension_id": {
          "type": "integer",
          "description": "The user's chosen extension_id from list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • remove_keyword changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id",
        "term"
      ],
      "properties": {
        "term": {
          "type": "string",
          "description": "As reported by list_keywords."
        },
        "locale": {
          "type": "string",
          "description": "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 \"de\" are one keyword and \"pt-br\" comes back as \"pt-BR\"."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • add_extension unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "chrome_url": {
          "type": "string",
          "maxLength": 2048,
          "description": "HTTPS Chrome Web Store listing URL; at least one store URL is required."
        },
        "firefox_url": {
          "type": "string",
          "maxLength": 2048,
          "description": "HTTPS Firefox Add-ons listing URL, optionally paired with the same product's Chrome URL."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • add_keyword changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id",
        "term"
      ],
      "properties": {
        "term": {
          "type": "string",
          "description": "The search term, e.g. \"json viewer\". Squished and lowercased before use."
        },
        "locale": {
          "type": "string",
          "description": "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 \"de\" are one keyword and \"pt-br\" comes back as \"pt-BR\"."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • add_competitor changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id",
        "store",
        "external_id"
      ],
      "properties": {
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string"
        },
        "external_id": {
          "type": "string",
          "description": "Chrome's 32-letter id or the AMO slug, as a search_catalog row's id gives it."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • remove_competitor changes data unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "extension_id",
        "store",
        "external_id"
      ],
      "properties": {
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string"
        },
        "external_id": {
          "type": "string",
          "description": "From list_competitors."
        },
        "extension_id": {
          "type": "integer",
          "description": "From list_extensions."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_listing unknown 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "store",
        "external_id"
      ],
      "properties": {
        "store": {
          "enum": [
            "chrome",
            "firefox"
          ],
          "type": "string"
        },
        "external_id": {
          "type": "string",
          "maxLength": 100,
          "description": "Chrome's 32-letter id or the AMO slug, as a search_catalog row's id gives it."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2b639d4d6b73db3c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2b639d4d6b73db3c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2b639d4d6b73db3c/badge.svg)](https://brick.blue/agent/2b639d4d6b73db3c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.