# Untapped Index Watch (mcpb · untapped-index-watch-mcp-0.2.0.mcpb)

Is every page in Google's index?

- Trust score: 41/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `untapped-index-watch-mcp-0.2.0.mcpb`: 41/100 (this document), [markdown](https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp.md), [page](https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/CTF-Max/untapped-plugins/releases/download/v0.2.0/untapped-index-watch-mcp-0.2.0.mcpb`
- Version: `0.2.0`
- Transport: `stdio`
- SHA-256: `7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - 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).
  - Install-script risk not yet assessed.
  - 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).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 283 tokens (~47/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

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

## Install

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

- Download bundle: `https://github.com/CTF-Max/untapped-plugins/releases/download/v0.2.0/untapped-index-watch-mcp-0.2.0.mcpb`
- SHA-256: `7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707`

### Verify on macOS / Linux

```bash
echo "7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707  untapped-index-watch-mcp-0.2.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\untapped-index-watch-mcp-0.2.0.mcpb).Hash -eq "7ce5216b8f1b35def8384d4100c86a94375ca1574bae274b5516d07d9446a707"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 41, +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.

### 2026-11-02 (score 40, +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.

### 2026-10-31 (score 39, +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.

### 2026-10-29 (score 38, +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.

### 2026-10-27 (score 37, +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.

### 2026-10-25 (score 36, +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.

### 2026-10-23 (score 35, +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.

### 2026-10-22 (score 34)

First indexed and scored.

## MCP tools (6)

### `google_login` (~43 tokens)

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.

### `google_login_status` (~33 tokens)

Free. Whether a Google OAuth client is configured, whether you are signed in, and how a pending sign-in went.

### `google_logout` (~24 tokens)

Revoke the saved Google sign-in at Google and delete it from this computer.

### `gsc_sites` (~23 tokens)

Free. List the Search Console properties your Google sign-in can see.

### `index_check` (~117 tokens)

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

Input parameters:

- `max_urls` (integer): default 50
- `site` (string, required): example.com, sc-domain:example.com or https://example.com/
- `sitemap_url` (string)
- `urls` (array)

### `index_history` (~43 tokens)

Free, local. Past index checks for a site (counts per run), or one URL's history.

Input parameters:

- `site` (string, required)
- `url` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp#diagnostics

## Score history

- 2026-11-05: 41
- 2026-11-04: 40
- 2026-11-03: 40
- 2026-11-02: 40
- 2026-11-01: 39
- 2026-10-31: 39
- 2026-10-30: 38
- 2026-10-29: 38
- 2026-10-28: 37
- 2026-10-27: 37
- 2026-10-26: 36
- 2026-10-25: 36
- 2026-10-24: 35
- 2026-10-23: 35
- 2026-10-22: 34

## Common questions

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

### What did VerifyMCP test on the Untapped Index Watch MCP server?

VerifyMCP ran 12 checks on Untapped Index Watch, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Untapped Index Watch: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/CTF-Max/untapped-plugins
- Website: https://github.com/CTF-Max/untapped-plugins/tree/main/untapped-index-watch#readme
- Changelog RSS feed: https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ctf-max-untapped-index-watch/untapped-index-watch-mcp