# HasData Google Scholar (remote · mcp.hasdata.com)

Google Scholar search results, citation counts and citation export formats, as structured JSON.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `mcp.hasdata.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-google-scholar/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-scholar/mcp)
- npm · `@hasdata/google-scholar-mcp`: 49/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-scholar/hasdata-google-scholar-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-scholar/hasdata-google-scholar-mcp)
- pypi · `hasdata-google-scholar-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-scholar/hasdata-google-scholar-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-google-scholar/hasdata-google-scholar-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=google_scholar`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-17.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1349 tokens (~192/item across 7 items; 3 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the HasData Google Scholar MCP server?

HasData Google Scholar is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=google_scholar, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-hasdata-google-scholar 'https://mcp.hasdata.com/mcp?apis=google_scholar'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-google-scholar": {
      "url": "https://mcp.hasdata.com/mcp?apis=google_scholar"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-google-scholar": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_scholar"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-google-scholar]
url = "https://mcp.hasdata.com/mcp?apis=google_scholar"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-google-scholar": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=google_scholar",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-google-scholar --url 'https://mcp.hasdata.com/mcp?apis=google_scholar' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-google-scholar:
    url: "https://mcp.hasdata.com/mcp?apis=google_scholar"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-google-scholar": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=google_scholar"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-google-scholar -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=google_scholar'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-google-scholar": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_scholar"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-17 (score 86, +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-14 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 83, +44)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.13
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-28 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 39)

First indexed and scored.

## MCP tools (3)

### `hasdata_google_scholar_case_law_getScholarCaseLawOpinion` (~227 tokens)

google_scholar_case_law: GET /

Get Scholar Case Law Opinion

Looks up a Google Scholar Case Law opinion by its `caseId` (as returned in a google/scholar organic result's `caseId`, when searching with `asSdt` set to a case-law court scope, or in another case-law result's `citedCases`). Returns the case title, party names, court, procedural history, argued/decided dates, short citations, docket numbers, and every case cited within the opinion (grouped by cited case with a ready-to-call `hasdataLink`). Use to build legal-research and case-law-analysis workflows, or to walk a citation graph one cited case at a time.

Input parameters:

- `caseId` (string, required): The `caseId` of a Google Scholar case-law result, as returned by the google/scholar endpoint.
- `hl` (string): The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.

### `hasdata_google_scholar_cite_getScholarCitationFormats` (~181 tokens)

google_scholar_cite: GET /

Get Scholar Citation Formats

Looks up citation formats and export links for a single Google Scholar organic search result, identified by its `resultId` (as returned in a google/scholar organic result). Returns formatted citation snippets (MLA, APA, Chicago, Harvard, Vancouver) and reference-manager export links (BibTeX, EndNote, RefMan, RefWorks). Use to build citation/bibliography features or complete a research workflow started with google/scholar.

Input parameters:

- `hl` (string): The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
- `q` (string, required): The `resultId` of a Google Scholar organic result, as returned by the google/scholar endpoint.

### `hasdata_google_scholar_scholar_getScholarSearchResults` (~683 tokens)

google_scholar_scholar: GET /

Get Scholar Search Results

Scrapes Google Scholar for a query with author:/source: search helpers, year range (asYlo/asYhi), cited-by and all-versions lookups (cites/cluster), review-article and citation-inclusion filters, language/language-restrict, start/num pagination, and asSdt to scope to case law (asSdt=2006 for all courts, 2003 for Federal courts only, or 4/6/3 plus comma-separated court codes for specific courts) or toggle patents. Returns each organic result with title, link, snippet, publication info (authors with profile links), cited-by count and link, related-articles link, and all-versions count and link; a case-law result links to a scholar_case?case= page and carries a ready-to-call caseHasdataLink. Use for academic research, literature review automation, citation tracking, grounding research agents with scholarly sources, and walking case law straight into google/scholar-case-law.

Input parameters:

- `asRr` (number): Set to 1 to return review articles only, or 0 (default) to return all articles.
- `asSdt` (string): Search type/filter. Pick a value below to search case law from a specific court, or use `0,5` for Articles (default) / `7` to include patents. Any comma-separated court-code combination Google Schola…
- `asVis` (number): Set to 1 to exclude citations from the results, or 0 (default) to include them.
- `asYhi` (number): Return results published up to and including this year.
- `asYlo` (number): Return results published from this year onward.
- `cites` (string): Unique article ID to look up articles that cite it, as returned in a result's `citedBy.citesId`.
- `cluster` (string): Unique article ID to look up all indexed versions of that article, as returned in a result's `versions.clusterId`.
- `filter` (number): Defines whether to enable or disable the filters for 'Similar Results' and 'Omitted Results'. Set to 1 (default) to enable these filters, or 0 to disable them.
- `hl` (string): The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
- `lr` (array): The 'lr' parameter specifies the language of the websites to return results from. This parameter filters results based on the language of the web content.
- `num` (number): Maximum number of results to return per page.
- `q` (string, required): Search query. Supports Google Scholar search helpers such as `author:` and `source:`.
- `safe` (string): Adult content filtering option.
- `scisbd` (number): Sort results by date instead of relevance: 1 for abstracts only, 2 for everything. Omit for relevance sorting.
- `start` (number): Result offset for pagination, where 0 is the first result.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hasdata-google-scholar/mcp#diagnostics

## Score history

- 2026-10-17: 86
- 2026-10-16: 85
- 2026-10-15: 85
- 2026-10-14: 85
- 2026-10-13: 84
- 2026-10-12: 84
- 2026-10-10: 83
- 2026-10-05: 39
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39

## Common questions

### What is the HasData Google Scholar MCP server?

HasData Google Scholar is an MCP server listed in the public MCP registry as com.hasdata/google-scholar. Google Scholar search results, citation counts and citation export formats, as structured JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=google_scholar).

### Is the HasData Google Scholar MCP server safe to use?

HasData Google Scholar scores 86 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 HasData Google Scholar MCP server expose?

HasData Google Scholar exposes 3 tools: hasdata_google_scholar_case_law_getScholarCaseLawOpinion, hasdata_google_scholar_cite_getScholarCitationFormats, hasdata_google_scholar_scholar_getScholarSearchResults. Their descriptions and schemas cost roughly 1,091 tokens of context every time the server is loaded.

### Does the HasData Google Scholar MCP server require authentication?

Yes. HasData Google Scholar asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the HasData Google Scholar MCP server still maintained?

HasData Google Scholar is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.hasdata.com/mcp?apis=google_scholar
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/google-scholar-mcp
- Website: https://docs.hasdata.com/apis/google-scholar/scholar
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-google-scholar/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-google-scholar/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-google-scholar/mcp