FastMCP server for scholarly papers, patents, books and standards with docling PDF conversion
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.
SCHOLAR_GITHUB_TOKENAPI keyoptionalGitHub token used to raise rate limits when fetching standards documents from GitHub. Optional; unauthenticated requests work at reduced limits.
SCHOLAR_MCP_S2_API_KEYAPI keyoptionalSemantic 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 keyoptionalAPI key for the VLM endpoint.
SCHOLAR_MCP_EPO_CONSUMER_KEYAPI keyoptionalEPO 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 keyoptionalEPO Open Patent Services consumer secret. Optional; patent tools are hidden when unset.
SCHOLAR_MCP_GOOGLE_BOOKS_API_KEYAPI keyoptionalGoogle Books API key. Optional; book tools work unauthenticated at reduced rate limits.
SCHOLAR_MCP_BEARER_TOKENAPI keyoptionalSingle shared bearer token; enables bearer auth unless `bearer_tokens_file` is set, which takes precedence.
SCHOLAR_MCP_OIDC_CLIENT_SECRETOAuth appoptionalOIDC client secret registered with the provider.
SCHOLAR_MCP_OIDC_JWT_SIGNING_KEYAPI keyoptionalSigning 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 keyoptionalValidate 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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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”.
FastMCP server for scholarly papers, patents, books and standards with docling PDF conversion
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.