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.

Untapped SERP

MCPB · UNTAPPED-SERP-MCP-0.2.0.MCPB

Real Google results and search volume

37 Trust /100

Last scanned (4 hours ago)

Scores higher than 75% of MCPB 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 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
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 476 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

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.

  • 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 36

    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 23 Oct 2026 · Analysed mcpb/https://github.com/CTF-Max/untapped-plugins/releases/download/v0.2.0/untapped-serp-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 →

MCP tools · 4 exposed · ~476 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
google_search_volume ~147

Google Ads monthly search volume, CPC and competition for up to 100 keywords (1000 with allow_large_batch). Paid (about $0.09 per call, any keyword count); cached 30 days. null volume means no data, never zero.

NameTypeReqDescription
allow_large_batchboolean––
dry_runboolean––
keywordsarrayyes–
language_codestring–default 'en'
location_codeinteger–DataForSEO location code (instead of location_name)
location_namestring–e.g. 'Palm Coast,Florida,United States' (default 'United States')
max_age_hoursnumber––

No output schema declared.

No examples provided.

google_serp ~229

Live Google organic results for one keyword in one place: positions, People Also Ask, local pack, AI Overview cited domains, featured snippet, and every position a target domain holds. Paid (user's DataForSEO account, about $0.002 per 10 results); cached 24 h.

NameTypeReqDescription
depthinteger–results to fetch; billed per 10
devicestring––
dry_runboolean–show the request and its cost reserve without calling
keywordstringyes–
language_codestring–default 'en'
location_codeinteger–DataForSEO location code (instead of location_name)
location_coordinatestring–'lat,lng[,radius_km]' (instead of location_name)
location_namestring–e.g. 'Palm Coast,Florida,United States' (default 'United States')
max_age_hoursnumber–reuse a cached result this fresh; 0 = fresh call
target_domainstring–hostname to locate, e.g. example.com

No output schema declared.

No examples provided.

serp_estimate ~52

Free. The cost reserve for a would-be google_serp or google_search_volume call and whether today's cap allows it. Never calls the API.

NameTypeReqDescription
argumentsobjectyes–
toolstringyes–

No output schema declared.

No examples provided.

serp_spend ~48

Free. Today's and this month's DataForSEO spend through this plugin, the daily cap, cache hits, the last 10 calls, and whether the credential variables are set (never their values).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Untapped SERP MCP server?

Untapped SERP 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, 39d0d111658c04d0219e4fa3a29cda514a33f8cce6926d7bf42d8f684880d658; the commands to do that are on this page. If it does not match, do not open it.

mcpb · untapped-serp-mcp-0.2.0.mcpb

Download bundle

Check 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

39d0d111658c04d0219e4fa3a29cda514a33f8cce6926d7bf42d8f684880d658

macOS / Linux

echo "39d0d111658c04d0219e4fa3a29cda514a33f8cce6926d7bf42d8f684880d658  untapped-serp-mcp-0.2.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\untapped-serp-mcp-0.2.0.mcpb).Hash -eq "39d0d111658c04d0219e4fa3a29cda514a33f8cce6926d7bf42d8f684880d658"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Untapped SERP MCP server?

Untapped SERP is an MCP server listed in the public MCP registry as io.github.CTF-Max/untapped-serp. Real Google results and search volume. This page covers its MCPB bundle (https://github.com/CTF-Max/untapped-plugins/releases/download/v0.2.0/untapped-serp-mcp-0.2.0.mcpb).

Is the Untapped SERP MCP server safe to use?

Untapped SERP scores 37 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 SERP MCP server expose?

Untapped SERP exposes 4 tools: google_serp, google_search_volume, serp_spend, serp_estimate. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

What licence is the Untapped SERP MCP server under?

Untapped SERP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.