io.github.xplormityai/searchdock-cli
NPM · SEARCHDOCK-CLI
Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI.
Available components
Last scanned (18 hours ago)
Scores higher than 77% of npm servers
Category Marketing and SEO
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to xplormityai/searchdock-cli). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability46
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 325 tokens (~65/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +24
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: poor functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
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 4 Nov 2026 · Analysed npm/searchdock-cli@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | xplormityai/searchdock-cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/xplormityai/searchdock-cli/.github/workflows/release.yml@refs/tags/v0.1.3 |
| Rekor log index | 3208681612 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3a5fd6f7c623ce6c5f401f33585d5ed91656e5975ed084952d7037791cce94194eb0caf4106176b45cf8518bac9ef0c403ca967200ce162e55160118b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
searchdock_analytics ~99
Read finalized search performance. Dates use Pacific Time. Missing query rows do not prove zero demand.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| days | integer | – | – |
| dimensions | array | – | – |
| end | string | – | – |
| limit | integer | – | – |
| profile | string | – | – |
| provider | string | – | – |
| site | string | – | – |
| start | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
searchdock_inspect ~54
Inspect the indexed version of a URL. Cannot perform live tests or request indexing.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | – |
| provider | string | – | – |
| site | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
searchdock_report ~96
Read search metrics, sitemap issues and optionally indexed status for specific URLs. Does not expose the full Page indexing exclusions report.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| days | integer | – | – |
| end | string | – | – |
| limit | integer | – | – |
| profile | string | – | – |
| provider | string | – | – |
| site | string | – | – |
| start | string | – | – |
| urls | array | – | – |
No output schema declared.
No examples provided.
searchdock_sitemaps ~41
Read sitemap processing status, errors and warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | – |
| provider | string | – | – |
| site | string | – | – |
No output schema declared.
No examples provided.
searchdock_sites ~35
List properties available to an already connected Google Search Console profile.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.xplormityai/searchdock-cli MCP server?
io.github.xplormityai/searchdock-cli runs locally as an npm package, launched with npx -y searchdock-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · searchdock-cli
claude mcp add xplormityai-searchdock-cli -- npx -y searchdock-cli
What is the io.github.xplormityai/searchdock-cli MCP server?
io.github.xplormityai/searchdock-cli is an MCP server listed in the public MCP registry as io.github.xplormityai/searchdock-cli. Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI. This page covers its npm package (searchdock-cli).
Is the io.github.xplormityai/searchdock-cli MCP server safe to use?
io.github.xplormityai/searchdock-cli scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.xplormityai/searchdock-cli MCP server expose?
io.github.xplormityai/searchdock-cli exposes 5 tools: searchdock_sites, searchdock_analytics, searchdock_sitemaps, searchdock_inspect, searchdock_report. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.
Is the io.github.xplormityai/searchdock-cli MCP server still maintained?
io.github.xplormityai/searchdock-cli is still listed as active in the MCP registry. We last reached this channel on 4 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.xplormityai/searchdock-cli MCP server under?
io.github.xplormityai/searchdock-cli declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.