Is Semantic Scholar MCP Server safe to use?

Semantic Scholar MCP Server has an HVTrust score of 78.2/100 (Grade B), ranked #168 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Semantic Scholar MCP Server?

Semantic Scholar MCP Server scores 78.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 22 GitHub stars and is categorized under MCP Servers.

Semantic Scholar MCP Server

smaniches/semantic-scholar-mcp

Semantic Scholar MCP server: 14 typed tools for paper search, citation graphs, author profiles, recommendations, PyPI/Docker.

MCP Servers Python Listed MIT

Is Semantic Scholar MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.4 / 10

Provenance Attested

Signed commits 72%

Last push 5d ago

Compare Semantic Scholar MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Semantic Scholar MCP Server scores 78.2/100 (Grade B), ranked #168 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.4/10; 72% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Semantic Scholar MCP Server compares in MCP Servers

#89 build123d MCP 78.5 +0.3
#90 Ai Cli MCP 78.4 +0.2
#91 Semantic Scholar MCP Server 78.2 this agent
#92 Deepseek MCP Server 78.0 −0.2
#93 MCP Rubber Duck 77.9 −0.3

Bars show each HVTrust score; the tick marks Semantic Scholar MCP Server’s 78.2.

Where the 78.2 comes from

HVTrust dimensions vs the MCP Servers average

78.2 / 100 · 100.0% confidence

Semantic Scholar MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.3 / 25

10.0 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.8 / 17

2.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.3 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.7 / 20

0.5 below avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with another agent Get email alerts for Semantic Scholar MCP Server View MCP Servers Report missing data

45.3

Activity sub-score · out of 100

#91

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 B 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

359

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #167

Analysis

Activity Inputs

45.3 / 100

StarsRepository reach

8.2 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.4 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

72%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 9

SAST 10

Security-Policy 3

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Common questions about Semantic Scholar MCP Server

Public supply-chain signals for Semantic Scholar MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Semantic Scholar MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does Semantic Scholar MCP Server publish package provenance?

Yes. Semantic Scholar MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Semantic Scholar MCP Server have an OpenSSF Scorecard?

Semantic Scholar MCP Server has an OpenSSF Scorecard score of 7.4/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 Semantic Scholar MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Semantic Scholar MCP Server use?

Semantic Scholar MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Semantic Scholar MCP Server's commits signed?

72% of the last 100 commits to Semantic Scholar MCP Server 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

Semantic Scholar MCP Server 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 Semantic Scholar MCP Server'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-09-23

Provenance Added

Package provenance attestation detected

Maintain Semantic Scholar MCP Server?

For maintainers

HVTrust scores Semantic Scholar MCP Server 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 585 spots (#753 → #168)

2026-09-23

HVTrust Changed

HVTrust up 48.4pts (29.9 → 78.3)

2026-09-22

Newly Listed

First tracked at rank #753

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Grade Changed

Trust grade A → B

2026-09-17

Rank Moved

Rank dropped 36 spots (#127 → #163)

2026-09-16

Rank Moved

Rank dropped 11 spots (#116 → #127)

2026-09-05

Rank Moved

Rank dropped 26 spots (#82 → #108)

2026-08-26

Scorecard Added

OSSF Scorecard: 7.3/10

2026-08-26

Grade Changed

Trust grade B → A

2026-08-26

Rank Moved

Rank rose 146 spots (#222 → #76)

2026-08-26

HVTrust Changed

HVTrust up 15.3pts (65.8 → 81.1)

2026-08-24

Rank Moved

Rank dropped 12 spots (#203 → #215)

2026-08-22

Rank Moved

Rank rose 12 spots (#217 → #205)

2026-08-19

Rank Moved

Rank dropped 17 spots (#204 → #221)

2026-08-17

Rank Moved

Rank rose 25 spots (#230 → #205)

2026-08-16

Rank Moved

Rank dropped 13 spots (#217 → #230)

2026-08-13

Rank Moved

Rank dropped 26 spots (#189 → #215)

2026-08-12

Rank Moved

Rank rose 16 spots (#205 → #189)

2026-08-10

Rank Moved

Rank dropped 10 spots (#196 → #206)

2026-08-08

Newly Listed

First tracked at rank #195

GitHub → PyPI: s2-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/semantic-scholar-mcp-server.svg)](https://hvtracker.net/agents/semantic-scholar-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/semantic-scholar-mcp-server"><img src="https://hvtracker.net/badge/semantic-scholar-mcp-server.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