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.

io.github.dotbrainhq/dottide

PYPI · DOTTIDE

Read-only Search Console, GA4, Bing and store numbers for every site, across Google accounts.

Available components

+3 this week 72 Trust /100

Last scanned (47 minutes ago)

Scores higher than 67% of PyPI servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 48 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1331 tokens (~121/item across 11 items; 11 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +1
    • Stability: 0.00 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Schema quality: fair → good functional
    • Package version: 0.4.0 → 0.4.1 functional
  • 28 Oct 26 68

    First indexed and scored.

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 5 Nov 2026 · Analysed pypi/dottide@0.4.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 48 packages
Packages resolved 48
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,285 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
bing_queries ~87

Bing Webmaster Tools clicks, impressions and average position by query, plus site totals, for a range. Bing feeds Copilot. Needs a [bing] key in the site's profile. Bing updates these numbers about once a week.

NameTypeReqDescription
daysinteger––
end–––
limitinteger––
sitestringyes–
start–––

No output schema declared.

No examples provided.

competing_pages ~133

Queries where two or more pages of the site each get at least `min_impressions`, so they split the clicks (cannibalization). For each query: every page with its clicks, impressions and position, the page with most clicks and its share. Biggest overlaps first. Same dates and filters as search_queries.

NameTypeReqDescription
country–––
daysinteger––
device–––
end–––
limitinteger––
min_impressionsinteger––
search_typestring––
sitestringyes–
start–––

No output schema declared.

No examples provided.

core_web_vitals ~130

Core Web Vitals for a page (default: the site's home page) from PageSpeed Insights. page_field and site_field hold real-user 75th-percentile LCP, INP and CLS with Google's good / needs improvement / poor rating, when Google has enough visits; lab holds one Lighthouse run (performance score, LCP, CLS, TBT, FCP, Speed Index). strategy is "mobile" or "desktop". One run takes 10 to 30 seconds.

NameTypeReqDescription
page–––
sitestringyes–
strategystring––

No output schema declared.

No examples provided.

discover ~82

Every Search Console property and GA4 web stream the key can read, matched by domain, with ready-to-paste [[sites]] blocks for any site not in a profile yet. Each block has a commented-out brand_terms suggestion from the domain name. Reads only; the user adds the blocks with `dottide discover --write`.

NameTypeReqDescription
profile–––

No output schema declared.

No examples provided.

index_health ~125

Is the site healthy in Google's index? Every sitemap Search Console knows (errors, warnings, when Google last read it, URLs submitted) and the index status of the top `pages` pages by clicks over the last `days` days (verdict, coverage, last crawl, Google's chosen canonical). `problems` lists anything to fix in plain words. Reads only: it never submits a sitemap or requests indexing. Each page checked uses one URL Inspection call.

NameTypeReqDescription
daysinteger––
pagesinteger––
sitestringyes–

No output schema declared.

No examples provided.

opportunities ~210

What to work on next for a site, from Search Console: queries in striking distance (position 8 to 20, by impressions), pages and queries that lost the most clicks against the previous period, pages and queries whose average position dropped the most (slipping_pages, slipping_queries, with min_impressions in both periods), and page-one queries whose CTR is under half the site's own median for that position. When low_ctr is empty because no position band has three queries, low_ctr_note says so and low_ctr_band_counts gives each band's count. Every item carries its numbers. Same date rules and filters as search_queries, except Discover and Google News, which have no query rows.

NameTypeReqDescription
country–––
daysinteger––
device–––
end–––
limitinteger––
min_impressionsinteger––
search_typestring––
sitestringyes–
start–––

No output schema declared.

No examples provided.

page_queries ~131

The queries that bring people to one page (full URL), with the page's own totals and `hidden`: the clicks and impressions Search Console counts for the page but leaves out of its query rows, because Google anonymizes rare queries. Same dates, compare and filters as search_queries.

NameTypeReqDescription
compareboolean––
country–––
daysinteger––
device–––
end–––
limitinteger––
pagestringyes–
search_typestring––
sitestringyes–
start–––

No output schema declared.

No examples provided.

search_queries ~202

Search Console clicks, impressions, CTR (percent) and average position, by "query" or "page". Dates are YYYY-MM-DD; without them the range is the last `days` days ending three days ago. compare=true adds the previous period of the same length and the change. Optional filters: country (three-letter ISO code like "usa"), device ("desktop", "mobile" or "tablet") and search_type ("web", "image", "video", "news", "discover" or "googleNews"; default "web"). Discover and Google News have page rows only. The result echoes the filters it used.

NameTypeReqDescription
bystring––
compareboolean––
country–––
daysinteger––
device–––
end–––
limitinteger––
search_typestring––
sitestringyes–
start–––

No output schema declared.

No examples provided.

sites ~33

Every configured site, which key covers it, and whether Search Console and GA4 access works at the moment of the call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

store_stats ~51

Live public store numbers that need no keys: WordPress.org plugins (installs, rating, downloads last 7 days), Firefox Add-ons (daily users, ratings), GitHub stars.

NameTypeReqDescription
profile–––

No output schema declared.

No examples provided.

traffic ~101

GA4 sessions by source and medium, plus AI assistant referrals (ChatGPT, Perplexity, Copilot, Gemini, Claude and others) totalled separately. Each assistant lists the landing_pages its visits started on, most sessions first. Only for sites with GA4.

NameTypeReqDescription
compareboolean––
daysinteger––
end–––
limitinteger––
sitestringyes–
start–––

No output schema declared.

No examples provided.

Install

How do I install the io.github.dotbrainhq/dottide MCP server?

io.github.dotbrainhq/dottide runs locally as a PyPI package, launched with uvx dottide. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · dottide

# add to Claude Code
claude mcp add dotbrainhq-dottide -- uvx dottide
Common questions

What is the io.github.dotbrainhq/dottide MCP server?

io.github.dotbrainhq/dottide is an MCP server listed in the public MCP registry as io.github.dotbrainhq/dottide. Read-only Search Console, GA4, Bing and store numbers for every site, across Google accounts. This page covers its PyPI package (dottide).

Is the io.github.dotbrainhq/dottide MCP server safe to use?

io.github.dotbrainhq/dottide scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.dotbrainhq/dottide MCP server expose?

io.github.dotbrainhq/dottide exposes 11 tools: sites, search_queries, page_queries, traffic, store_stats, and 6 more. Their descriptions and schemas cost roughly 1,285 tokens of context every time the server is loaded.

Is the io.github.dotbrainhq/dottide MCP server still maintained?

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

What licence is the io.github.dotbrainhq/dottide MCP server under?

io.github.dotbrainhq/dottide declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.