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.

io.github.CloudCorpRecords/scholardata

NPM · @RENETURCIOS/SCHOLARDATA · 2 COMPONENTS

Google Scholar as JSON: scholarly search results, case-law opinions and citation formats.

0 this week 68 Trust /100

Last scanned (20 hours ago)

Scores higher than 39% of npm servers

Category Education and Research

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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1091 tokens (~363/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

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.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 53

    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 21 Nov 2026 · Analysed npm/@reneturcios/scholardata@0.1.0

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 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,091 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
hasdata_google_scholar_case_law_getScholarCaseLawOpinion ~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.

NameTypeReqDescription
caseIdstringyesThe `caseId` of a Google Scholar case-law result, as returned by the google/scholar endpoint.
hlstring–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 ~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.

NameTypeReqDescription
hlstring–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`.
qstringyesThe `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 ~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.

NameTypeReqDescription
asRrnumber–Set to 1 to return review articles only, or 0 (default) to return all articles.
asSdtstring–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…
asVisnumber–Set to 1 to exclude citations from the results, or 0 (default) to include them.
asYhinumber–Return results published up to and including this year.
asYlonumber–Return results published from this year onward.
citesstring–Unique article ID to look up articles that cite it, as returned in a result's `citedBy.citesId`.
clusterstring–Unique article ID to look up all indexed versions of that article, as returned in a result's `versions.clusterId`.
filternumber–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.
hlstring–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`.
lrarray–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.
numnumber–Maximum number of results to return per page.
qstringyesSearch query. Supports Google Scholar search helpers such as `author:` and `source:`.
safestring–Adult content filtering option.
scisbdnumber–Sort results by date instead of relevance: 1 for abstracts only, 2 for everything. Omit for relevance sorting.
startnumber–Result offset for pagination, where 0 is the first result.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/scholardata MCP server?

io.github.CloudCorpRecords/scholardata runs locally as an npm package, launched with npx -y @reneturcios/scholardata mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/scholardata

# add to Claude Code
claude mcp add cloudcorprecords-scholardata -- npx -y @reneturcios/scholardata mcp
Common questions

What is the io.github.CloudCorpRecords/scholardata MCP server?

io.github.CloudCorpRecords/scholardata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/scholardata. Google Scholar as JSON: scholarly search results, case-law opinions and citation formats. This page covers its npm package (@reneturcios/scholardata).

Is the io.github.CloudCorpRecords/scholardata MCP server safe to use?

io.github.CloudCorpRecords/scholardata scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.CloudCorpRecords/scholardata MCP server expose?

io.github.CloudCorpRecords/scholardata 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.

Is the io.github.CloudCorpRecords/scholardata MCP server still maintained?

io.github.CloudCorpRecords/scholardata is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/scholardata MCP server under?

io.github.CloudCorpRecords/scholardata 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 io.github.CloudCorpRecords/scholardata MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/scholardata, 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 io.github.CloudCorpRecords/scholardata: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.