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.

SearchLink Lite

NPM · SEARCHLINK-LITE · 2 COMPONENTS · SCANNED SEP 25

Google Search Console in your AI. Local, read-only, free and open source.

66 Trust /100
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 Security98
  • 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
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1185 tokens (~148/item across 8 items; 8 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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

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 SearchLink Lite MCP server?

SearchLink Lite runs locally as an npm package, launched with npx -y searchlink-lite. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · searchlink-lite

# add to Claude Code
claude mcp add com-namubase-searchlink-searchlink-lite -- npx -y searchlink-lite
// .cursor/mcp.json
{
  "mcpServers": {
    "com-namubase-searchlink-searchlink-lite": {
      "command": "npx",
      "args": [
        "-y",
        "searchlink-lite"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-namubase-searchlink-searchlink-lite": {
      "command": "npx",
      "args": [
        "-y",
        "searchlink-lite"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-namubase-searchlink-searchlink-lite -- npx -y searchlink-lite
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-namubase-searchlink-searchlink-lite": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "searchlink-lite"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-namubase-searchlink-searchlink-lite --command npx --arg -y --arg searchlink-lite
# ~/.hermes/config.yaml
mcp_servers:
  com-namubase-searchlink-searchlink-lite:
    command: "npx"
    args: ["-y", "searchlink-lite"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-namubase-searchlink-searchlink-lite": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "searchlink-lite"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-namubase-searchlink-searchlink-lite -t stdio -c npx -a -y searchlink-lite
// mcp.json
{
  "mcpServers": {
    "com-namubase-searchlink-searchlink-lite": {
      "command": "npx",
      "args": [
        "-y",
        "searchlink-lite"
      ]
    }
  }
}
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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +10
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 22 Sept 26 56

    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 25 Sept 2026 · Analysed npm/searchlink-lite@0.2.2

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,185 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
algorithm_updates ~81

Google's official ranking and spam update history from the Google Search Status Dashboard, with start and end dates. Use it when traffic changed suddenly, to see whether an update lines up, before blaming the site's own edits. Needs no credentials. Read-only.

NameTypeReqDescription
daysinteger–How many days back to list updates, 7 to 365. Default 90.

No output schema declared.

No examples provided.

find_opportunities ~187

Finds the quickest wins: queries seen often but rarely clicked (rewrite the title or description), queries ranking #8 to #20 (one push from page one), and pages losing clicks. Use when the user asks what to improve or where to start. Returns each item with its numbers and the suggested fix. Read-only.

NameTypeReqDescription
daysinteger–Length of the period in days, 7 to 480, ending about 3 days ago because Google data lags. It is compared with the same number of days right before it. Default 28.
limitinteger–Maximum items per kind of opportunity, 1 to 50. Default 15.
sitestringyesThe Search Console property to read. Accepts "example.com", "https://example.com/" or "sc-domain:example.com". Call list_sites first if unsure which properties exist.

No output schema declared.

No examples provided.

inspect_url ~151

Asks Google's URL Inspection API about one page: whether it is indexed, the coverage state, last crawl time, the canonical Google chose versus the one you declared, and robots or fetch problems. Use for "is this page on Google?" questions. For on-page problems use page_check. Read-only; Google allows about 2,000 inspections a day per property.

NameTypeReqDescription
sitestringyesThe Search Console property to read. Accepts "example.com", "https://example.com/" or "sc-domain:example.com". Call list_sites first if unsure which properties exist.
urlstringyesFull URL of the page to inspect, including https://. It must belong to the site given.

No output schema declared.

No examples provided.

list_sites ~60

Lists every Search Console property the credentials can read, with the access level of each. Call this first when the user has not named a site, or when another tool says a site was not found. Read-only. Returns a table of property URLs and permissions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

page_check ~97

Fetches one public page the way a search engine does and checks the title, meta description, canonical, noindex and robots.txt, H1 headings, word count, image alt text and structured data. Returns what it found and a list of problems in order of importance. Works without any Google credentials. Read-only: it only downloads the page.

NameTypeReqDescription
urlstringyesFull URL of any public page to check, including https://.

No output schema declared.

No examples provided.

search_performance ~325

Custom Search Console report when site_overview is not specific enough: group by query, page, country, device or date (up to two at once), filter by query or page text, sort, and optionally add the change against the previous period. Returns a table with clicks, impressions, CTR and position per row. Read-only.

NameTypeReqDescription
compare_previousboolean–Add each row's change against the previous period of the same length. Default false.
daysinteger–Length of the period in days, 7 to 480, ending about 3 days ago because Google data lags. It is compared with the same number of days right before it. Default 28.
filter_pagestring–Keep only pages whose URL contains this text, e.g. "/blog/".
filter_querystring–Keep only search queries that contain this text (case-insensitive), e.g. a brand or product name.
group_byarray–One or two dimensions to break the numbers down by, e.g. ["query"] or ["page", "query"]. Default ["query"].
limitinteger–Maximum rows to return, 1 to 200. Default 25.
sitestringyesThe Search Console property to read. Accepts "example.com", "https://example.com/" or "sc-domain:example.com". Call list_sites first if unsure which properties exist.
sort_bystring–Which number to sort rows by, highest first (position: best first). Default clicks.

No output schema declared.

No examples provided.

site_overview ~178

The first tool to call for any question about how a site is doing on Google. Returns total clicks, impressions, CTR and average position for the period against the period before (totals match the Search Console UI), the pages that gained and lost the most clicks, and up to 3 plain-language things to do now. For custom breakdowns use search_performance instead. Read-only.

NameTypeReqDescription
daysinteger–Length of the period in days, 7 to 480, ending about 3 days ago because Google data lags. It is compared with the same number of days right before it. Default 28.
sitestringyesThe Search Console property to read. Accepts "example.com", "https://example.com/" or "sc-domain:example.com". Call list_sites first if unsure which properties exist.

No output schema declared.

No examples provided.

sitemaps ~106

Lists the sitemaps submitted for the site in Search Console, with when Google last read each one, errors, warnings and how many URLs it contains. Use for indexing questions about many pages at once. Read-only; it does not submit or change sitemaps.

NameTypeReqDescription
sitestringyesThe Search Console property to read. Accepts "example.com", "https://example.com/" or "sc-domain:example.com". Call list_sites first if unsure which properties exist.

No output schema declared.

No examples provided.

Common questions

What is the SearchLink Lite MCP server?

SearchLink Lite is an MCP server listed in the public MCP registry as com.namubase.searchlink/searchlink-lite. Google Search Console in your AI. Local, read-only, free and open source. This page covers its npm package (searchlink-lite).

Is the SearchLink Lite MCP server safe to use?

SearchLink Lite scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 SearchLink Lite MCP server expose?

SearchLink Lite exposes 8 tools: list_sites, site_overview, search_performance, find_opportunities, inspect_url, and 3 more. Their descriptions and schemas cost roughly 1,185 tokens of context every time the server is loaded.

Is the SearchLink Lite MCP server still maintained?

SearchLink Lite is still listed as active in the MCP registry. We last reached this channel on 25 September 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 SearchLink Lite MCP server under?

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