updated 2026-09-26 06:32 UTC

Scopus MCP

qwe4559999/scopus-mcp

A Model Context Protocol (MCP) server for Elsevier Scopus. Allows AI assistants like Claude to search academic papers, retrieve abstracts, and analyze author profiles directly.

MCP Servers Python Listed MIT

Is Scopus MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.3 / 10
Provenance None
Signed commits 29%
Last push 132d ago
Compare Scopus MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Scopus MCP scores 42.6/100 (Grade D), ranked #1110 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.3/10; 29% of recent commits are signed; last pushed 2026-05-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Scopus MCP compares in MCP Servers

  1. #653 Nslookup MCP 42.7 +0.1
  2. #654 WPFVisualTreeMcp 42.6 ±0
  3. #655 Scopus MCP 42.6 this agent
  4. #656 Spec Workflow MCP 42.5 −0.1
  5. #657 SocialGPT 42.4 −0.2

Bars show each HVTrust score; the tick marks Scopus MCP’s 42.6.

Where the 42.6 comes from

HVTrust dimensions vs the MCP Servers average

42.6 / 100 · 100.0% confidence

Scopus MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.6 / 25
4.7 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
0.9 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
3.2 / 20
8.9 below avg 12.1
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.5 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 124 spots (#1233 → #1109)
2026-09-23
HVTrust Changed
HVTrust up 25.9pts (16.7 → 42.6)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 132 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Scopus MCP View MCP Servers Report missing data
21.9
Activity sub-score · out of 100
#655
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 132 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
44
Forks
12
Last Push
2026-05-17
132 days ago
Commits (4 wk)
0
Downloads (7d)
119
pypi
HN mentions (30d)
—
Open Issues
3
Rank Change
▼3
was #1107

Analysis

Activity Inputs

21.9 / 100
StarsRepository reach
9.9 / 30
FreshnessLast push recency
6.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.3 / 10
OpenSSF Scorecard · scanned Sep 19, 2026
Signed Commits
29%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 0

Common questions about Scopus MCP

Public trust evidence for Scopus MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Scopus MCP publish package provenance?
No published build provenance is currently detected for Scopus MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Scopus MCP have an OpenSSF Scorecard?
Scopus MCP has an OpenSSF Scorecard score of 3.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Scopus MCP actively maintained?
Slowing down. Last push was 132 days ago — keep an eye on whether activity resumes.
What license does Scopus MCP use?
Scopus MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Scopus MCP's commits signed?
28% of the last 100 commits to Scopus MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Scopus MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Scopus MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-15
Activity Went Stale
No commits for 90 days

Maintain Scopus MCP?

For maintainers

HVTrust scores Scopus MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 21Listed 2HVTrust 2Stale 1Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 124 spots (#1233 → #1109)
2026-09-23
HVTrust Changed
HVTrust up 25.9pts (16.7 → 42.6)
2026-09-22
Newly Listed
First tracked at rank #1233
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank dropped 10 spots (#1089 → #1099)
2026-09-12
Rank Moved
Rank dropped 14 spots (#1075 → #1089)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1057 → #1071)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1046 → #1057)
2026-09-07
Rank Moved
Rank dropped 34 spots (#1012 → #1046)
2026-09-06
Rank Moved
Rank dropped 16 spots (#996 → #1012)
2026-09-05
Rank Moved
Rank dropped 50 spots (#946 → #996)
2026-09-04
Rank Moved
Rank dropped 25 spots (#921 → #946)
2026-09-03
Rank Moved
Rank dropped 54 spots (#867 → #921)
2026-09-02
Scorecard Added
OSSF Scorecard: 3.3/10
2026-09-02
Rank Moved
Rank rose 300 spots (#1167 → #867)
2026-09-02
HVTrust Changed
HVTrust up 17.7pts (26.5 → 44.2)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1125 → #1167)
2026-08-31
Rank Moved
Rank dropped 34 spots (#1091 → #1125)
2026-08-30
Rank Moved
Rank dropped 48 spots (#1043 → #1091)
2026-08-29
Rank Moved
Rank dropped 50 spots (#993 → #1043)
2026-08-28
Rank Moved
Rank dropped 36 spots (#957 → #993)
2026-08-27
Rank Moved
Rank dropped 27 spots (#930 → #957)
2026-08-26
Rank Moved
Rank dropped 113 spots (#817 → #930)
2026-08-16
Rank Moved
Rank dropped 17 spots (#796 → #813)
2026-08-15
Activity Went Stale
No commits for 90 days
2026-08-13
Rank Moved
Rank dropped 11 spots (#784 → #795)
2026-08-10
Rank Moved
Rank dropped 44 spots (#747 → #791)
2026-08-08
Newly Listed
First tracked at rank #742
GitHub → PyPI: scopus-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 42.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/scopus-mcp.svg)](https://hvtracker.net/agents/scopus-mcp)
HTML:
<a href="https://hvtracker.net/agents/scopus-mcp"><img src="https://hvtracker.net/badge/scopus-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON