pvliesdonk-scholar-mcp

MCPcommunity
v2.0.0io.github.pvliesdonkUnknownUpdated 22d agoGitHub

FastMCP server for scholarly papers, patents, books and standards with docling PDF conversion

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2GitHub stars
1Forks
22d agoLast update
Reads these credentials
  • SCHOLAR_GITHUB_TOKENAPI keyoptional

    GitHub token used to raise rate limits when fetching standards documents from GitHub. Optional; unauthenticated requests work at reduced limits.

  • SCHOLAR_MCP_S2_API_KEYAPI keyoptional

    Semantic Scholar API key. Optional but strongly recommended: unauthenticated requests are limited to ~1 req/s. Request one at https://www.semanticscholar.org/product/api#api-key-form.

  • SCHOLAR_MCP_VLM_API_KEYAPI keyoptional

    API key for the VLM endpoint.

  • SCHOLAR_MCP_EPO_CONSUMER_KEYAPI keyoptional

    EPO Open Patent Services consumer key. Optional; patent tools are hidden when unset. Register at https://developers.epo.org/user/register.

  • SCHOLAR_MCP_EPO_CONSUMER_SECRETAPI keyoptional

    EPO Open Patent Services consumer secret. Optional; patent tools are hidden when unset.

  • SCHOLAR_MCP_GOOGLE_BOOKS_API_KEYAPI keyoptional

    Google Books API key. Optional; book tools work unauthenticated at reduced rate limits.

  • SCHOLAR_MCP_BEARER_TOKENAPI keyoptional

    Single shared bearer token; enables bearer auth unless `bearer_tokens_file` is set, which takes precedence.

  • SCHOLAR_MCP_OIDC_CLIENT_SECRETOAuth appoptional

    OIDC client secret registered with the provider.

  • SCHOLAR_MCP_OIDC_JWT_SIGNING_KEYAPI keyoptional

    Signing key for issued tokens; used in oidc-proxy mode only. When unset, the key is derived deterministically from `oidc_client_secret`, so tokens survive a restart. Rotating that secret then…

  • SCHOLAR_MCP_OIDC_VERIFY_ACCESS_TOKENAPI keyoptional

    Validate the access token instead of the id token.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.pvliesdonk
LicenseUnknown
Version2.0.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv1.9.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

FastMCP server for scholarly papers, patents, books and standards with docling PDF conversion

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.