citation-network-mcp

MCPcommunity
v0.15.0io.github.michalhronUnknownUpdated 5d agoGitHub

Citation-network analysis on Scopus or OpenAlex: coupling, co-citation, lineages, bibliometrics.

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 →
5d agoLast update
Needs 1 credential before it runs
  • SCOPUS_API_KEYAPI keyrequired

    Elsevier API key from dev.elsevier.com (required to start the server).

  • SCOPUS_INSTTOKENAPI keyoptional

    Institutional token for subscriber access off campus.

  • OPENALEX_API_KEYAPI keyoptional

    Free OpenAlex key; raises the daily OpenAlex budget tenfold.

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.michalhron
LicenseUnknown
Version0.15.0
Sourcemcp-registry
GitHubmichalhron/citation-network-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · not run+0/30
→ Not yet scanned — the repository archive is scanned on the next cron run
—Obfuscation / exfil scan · not run+0/20
→ Not yet scanned — the repository archive is scanned on the next cron run
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedOct 2, 2026

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

Tools

Not scanned yet

Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.

About

Citation-network analysis on Scopus or OpenAlex: coupling, co-citation, lineages, bibliometrics.

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.