HasData Google Scholar
REMOTE · MCP.HASDATA.COM · 3 COMPONENTS
Google Scholar search results, citation counts and citation export formats, as structured JSON.
Last scanned (2 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 17 Oct 26 +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.
- 14 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +44
- Transport: unverified → pass ▲ security
- 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. security
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 28 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
- 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
- 22 Sept 26 39
First indexed and scored.
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 17 Oct 2026 · Probed https://mcp.hasdata.com/mcp?apis=google_scholar
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.hasdata.com | CN=YR1,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | RSA 2048 | SHA256-RSA | 5cef740443d03259c4ef72de38826f9d2a3 |
| SANs: mcp.hasdata.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.hasdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hasdata.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authorization is required: connect with OAuth or send an x-api-key header", scope="mcp:tools", resource_metadata="https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authorization is required: connect with OAuth or send an x-api-key header", scope="mcp:tools", resource_metadata="https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Document | https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.hasdata.com/mcp |
| Authorisation server | https://mcp.hasdata.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hasdata.com/mcp?apis=google_scholar | Verified | 200 | |
| http (plaintext) | http://mcp.hasdata.com/mcp?apis=google_scholar | HTTPS enforced | 308 | https://mcp.hasdata.com/mcp?apis=google_scholar |
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 →
hasdata_google_scholar_case_law_getScholarCaseLawOpinion google_scholar_case_law: GET / ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseId | string | yes | 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`. |
No output schema declared.
No examples provided.
hasdata_google_scholar_cite_getScholarCitationFormats google_scholar_cite: GET / ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The `resultId` of a Google Scholar organic result, as returned by the google/scholar endpoint. |
No output schema declared.
No examples provided.
hasdata_google_scholar_scholar_getScholarSearchResults google_scholar_scholar: GET / ~683
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · mcp.hasdata.com
claude mcp add --transport http com-hasdata-google-scholar 'https://mcp.hasdata.com/mcp?apis=google_scholar'
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.