Untapped Index Watch
MCPB · UNTAPPED-INDEX-WATCH-MCP-0.2.0.MCPB
Is every page in Google's index?
Available components
Last scanned (10 hours ago)
Scores higher than 73% of MCPB 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 283 tokens (~47/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "google_logout" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 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.
- 31 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.
- 29 Oct 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.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 34
First indexed and scored.
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 mcpb/https://github.com/CTF-Max/untapped-plugins/releases/download/v0.2.0/untapped-index-watch-mcp-0.2.0.mcpb@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
google_login ~43
Start Google sign-in (read-only Search Console). Opens the browser; returns the link too. Then call google_login_status. One sign-in serves every Untapped Google plugin.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
google_login_status ~33
Free. Whether a Google OAuth client is configured, whether you are signed in, and how a pending sign-in went.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
google_logout ~24
Revoke the saved Google sign-in at Google and delete it from this computer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gsc_sites ~23
Free. List the Search Console properties your Google sign-in can see.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
index_check ~117
Check whether each page of a site is in Google's index (Search Console URL Inspection), flag what needs attention with what to do, and compare with the last check. URLs come from the sitemap (default /sitemap.xml) or a list. Free (Google quota: 2,000 per site per day).
| Name | Type | Req | Description |
|---|---|---|---|
| max_urls | integer | – | default 50 |
| site | string | yes | example.com, sc-domain:example.com or https://example.com/ |
| sitemap_url | string | – | – |
| urls | array | – | – |
No output schema declared.
No examples provided.
index_history ~43
Free, local. Past index checks for a site (counts per run), or one URL's history.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | – |
| url | string | – | – |
No output schema declared.
No examples provided.
How do I install the Untapped Index Watch MCP server?
Untapped Index Watch ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707; the commands to do that are on this page. If it does not match, do not open it.
mcpb · untapped-index-watch-mcp-0.2.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707
macOS / Linux
echo "7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707 untapped-index-watch-mcp-0.2.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\untapped-index-watch-mcp-0.2.0.mcpb).Hash -eq "7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Untapped Index Watch MCP server?
Untapped Index Watch is an MCP server listed in the public MCP registry as io.github.CTF-Max/untapped-index-watch. Is every page in Google's index? This page covers its MCPB bundle (https://github.com/CTF-Max/untapped-plugins/releases/download/v0.2.0/untapped-index-watch-mcp-0.2.0.mcpb).
Is the Untapped Index Watch MCP server safe to use?
Untapped Index Watch scores 41 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 Untapped Index Watch MCP server expose?
Untapped Index Watch exposes 6 tools: google_login, google_login_status, google_logout, gsc_sites, index_check, index_history. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.
What licence is the Untapped Index Watch MCP server under?
Untapped Index Watch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.