updated 2026-11-11 00:08 UTC

Patsnap Patent & Literature Search

Repository Website

Search global patents across WIPO, EPO, USPTO, CNIPA, JPO, KIPO and other authorities, together with scientific literature from PubMed, arXiv, Nature, Science and other major sources using natural-language, semantic, keyword and structured search.

MCP Servers JavaScript Listed Apache-2.0

Is Patsnap Patent & Literature Search safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.5 / 10
Provenance None
Signed commits 30%
Last push 97d ago
Compare Patsnap Patent & Literature Search

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Patsnap Patent & Literature Search scores 37.3/100 (Grade D), ranked #1257 of 1387 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.5/10; 30% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Patsnap Patent & Literature Search could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Patsnap Patent & Literature Search and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/patsnap/patent-literature-search-mcp, Apache-2.0, last pushed 2026-08-06. 30% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.5/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages None

    No registry package. Patsnap Patent & Literature Search is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 3.9/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Patsnap Patent & Literature Search’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Patsnap Patent & Literature Search compares in MCP Servers

  1. #722 Hummingbot MCP 38.0 +0.7
  2. #723 MCP Power Automate 38.0 +0.7
  3. #724 Patsnap Patent & Literature Search 37.3 this agent
  4. #725 Workopia MCP 37.2 −0.1
  5. #726 MCP Funnel 37.1 −0.2

Bars show each HVTrust score; the tick marks Patsnap Patent & Literature Search’s 37.3.

Where the 37.3 comes from

HVTrust dimensions vs the MCP Servers average

37.3 / 100 · 100.0% confidence

Patsnap Patent & Literature Search MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.9 / 25
4.9 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
5.5 / 20
6.8 below avg 12.3
AdoptionLog-scaled stars · package downloads
4.6 / 20
3.0 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-04
Activity Went Stale
No commits for 90 days
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/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 97 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
27.2
Activity sub-score · out of 100
#724
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 97 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
85
Forks
6
Last Push
2026-08-06
97 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1257

Analysis

Activity Inputs

27.2 / 100
StarsRepository reach
11.6 / 30
FreshnessLast push recency
11.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.9 / 20

Common questions about Patsnap Patent & Literature Search

Public trust evidence for Patsnap Patent & Literature Search 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 Patsnap Patent & Literature Search publish package provenance?
No published build provenance is currently detected for Patsnap Patent & Literature Search. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Patsnap Patent & Literature Search have an OpenSSF Scorecard?
Patsnap Patent & Literature Search has an OpenSSF Scorecard score of 3.5/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 Patsnap Patent & Literature Search actively maintained?
Slowing down. Last push was 97 days ago — keep an eye on whether activity resumes.
What license does Patsnap Patent & Literature Search use?
Patsnap Patent & Literature Search ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Patsnap Patent & Literature Search's commits signed?
30% of the last 100 commits to Patsnap Patent & Literature Search 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
Declared
MCP support appears present, but direct server implementation is less certain.
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
N/A
No package source configured
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 Patsnap Patent & Literature Search'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-11-04
Activity Went Stale
No commits for 90 days
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain Patsnap Patent & Literature Search?

For maintainers

HVTrust scores Patsnap Patent & Literature Search 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 23Score 2HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1Stale 1
2026-11-04
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 11 spots (#1188 → #1199)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank dropped 492 spots (#662 → #1154)
2026-09-23
HVTrust Changed
HVTrust up 8.9pts (31.7 → 40.6)
2026-09-22
Newly Listed
First tracked at rank #662
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 15 spots (#1123 → #1138)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1105 → #1120)
2026-09-07
Rank Moved
Rank dropped 24 spots (#1073 → #1097)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1056 → #1073)
2026-09-05
Rank Moved
Rank dropped 72 spots (#984 → #1056)
2026-09-04
Rank Moved
Rank dropped 27 spots (#957 → #984)
2026-09-03
Rank Moved
Rank dropped 60 spots (#897 → #957)
2026-09-02
Rank Moved
Rank dropped 72 spots (#825 → #897)
2026-09-01
Rank Moved
Rank dropped 25 spots (#800 → #825)
2026-08-31
Rank Moved
Rank dropped 38 spots (#762 → #800)
2026-08-30
Rank Moved
Rank dropped 29 spots (#733 → #762)
2026-08-29
Rank Moved
Rank dropped 45 spots (#688 → #733)
2026-08-28
Rank Moved
Rank dropped 65 spots (#623 → #688)
2026-08-28
Activity Score Changed
Activity score down 5pts (45 → 40)
2026-08-27
Scorecard Added
OSSF Scorecard: 3.9/10
2026-08-27
Rank Moved
Rank rose 578 spots (#1201 → #623)
2026-08-27
HVTrust Changed
HVTrust up 27.6pts (18.4 → 46.0)
2026-08-26
Rank Moved
Rank dropped 42 spots (#1159 → #1201)
2026-08-24
Rank Moved
Rank dropped 13 spots (#1147 → #1160)
2026-08-23
Rank Moved
Rank dropped 32 spots (#1115 → #1147)
2026-08-23
Activity Score Changed
Activity score down 5pts (50 → 45)
2026-08-21
Rank Moved
Rank dropped 28 spots (#1091 → #1119)
2026-08-20
Rank Moved
Rank dropped 10 spots (#1081 → #1091)
2026-08-16
Rank Moved
Rank dropped 43 spots (#1044 → #1087)
2026-08-14
Rank Moved
Rank dropped 21 spots (#1027 → #1048)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 37.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/patsnap-patent-literature-search.svg)](https://hvtracker.net/agents/patsnap-patent-literature-search)
HTML:
<a href="https://hvtracker.net/agents/patsnap-patent-literature-search"><img src="https://hvtracker.net/badge/patsnap-patent-literature-search.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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