SearchLink Lite
NPM · SEARCHLINK-LITE · 2 COMPONENTS
Google Search Console in your AI. Local, read-only, free and open source.
Available components
Last scanned (8 hours ago)
Scores higher than 49% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 61 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Stability: 0.97 → pass security
- 20 Nov 26 0
- Stability: pass → 0.97 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Stability: 0.97 → pass security
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.87 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 22 Nov 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 →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
algorithm_updates Google 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days back to list updates, 7 to 365. Default 90. |
No output schema declared.
No examples provided.
find_opportunities 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 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. |
| limit | integer | – | Maximum items per kind of opportunity, 1 to 50. Default 15. |
| site | string | yes | The 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 Check if a page is indexed ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The 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. |
| url | string | yes | Full URL of the page to inspect, including https://. It must belong to the site given. |
No output schema declared.
No examples provided.
list_sites List my 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 Check one page ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of any public page to check, including https://. |
No output schema declared.
No examples provided.
search_performance Search performance (custom) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| compare_previous | boolean | – | Add each row's change against the previous period of the same length. Default false. |
| days | integer | – | 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_page | string | – | Keep only pages whose URL contains this text, e.g. "/blog/". |
| filter_query | string | – | Keep only search queries that contain this text (case-insensitive), e.g. a brand or product name. |
| group_by | array | – | One or two dimensions to break the numbers down by, e.g. ["query"] or ["page", "query"]. Default ["query"]. |
| limit | integer | – | Maximum rows to return, 1 to 200. Default 25. |
| site | string | yes | The 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_by | string | – | Which number to sort rows by, highest first (position: best first). Default clicks. |
No output schema declared.
No examples provided.
site_overview 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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | 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. |
| site | string | yes | The 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 Sitemap status ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The 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.
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
claude mcp add com-namubase-searchlink-searchlink-lite -- npx -y searchlink-lite
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 74 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 22 November 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 22 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 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.
What did VerifyMCP test on the SearchLink Lite MCP server?
VerifyMCP ran 15 checks on SearchLink Lite, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about SearchLink Lite: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.