Opentargets MCP

MCP server for Open Targets data

MCP Servers Python Listed MIT

Is Opentargets MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.6 / 10
Provenance Attested
Signed commits 6%
Last push 5d ago
Compare Opentargets MCP
Suggest a correction

In detail: Opentargets MCP scores 72.5/100 (Grade B), ranked #275 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 4.6/10; 6% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Opentargets MCP compares in MCP Servers

  1. #161 Configcat MCP Server 72.7 +0.2
  2. #162 Universal Screenshot MCP 72.6 +0.1
  3. #163 Opentargets MCP 72.5 this agent
  4. #164 Upstash MCP Server 72.5 ±0
  5. #165 MCP Zuul 72.4 −0.1

Bars show each HVTrust score; the tick marks Opentargets MCP’s 72.5.

Where the 72.5 comes from

HVTrust dimensions vs the MCP Servers average

72.5 / 100 · 100.0% confidence

Opentargets MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.6 / 25
3.3 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
12.4 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
17.4 / 20
5.3 above avg 12.1
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.1 below avg 7.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
54.5
Activity sub-score · out of 100
#163

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 →

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
19
Forks
8
Last Push
2026-09-21
5 days ago
Commits (4 wk)
26
Downloads (7d)
168
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #277

Analysis

Activity Inputs

54.5 / 100
StarsRepository reach
7.8 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
17.9 / 25
CommunityFork signal
4.4 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Sep 20, 2026
Signed Commits
6%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 5
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 10

Common questions about Opentargets MCP

Opentargets MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Opentargets MCP publish package provenance?
Yes. Opentargets MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Opentargets MCP have an OpenSSF Scorecard?
Opentargets MCP has an OpenSSF Scorecard score of 4.6/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 Opentargets MCP actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does Opentargets MCP use?
Opentargets MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Opentargets MCP's commits signed?
6% of the last 100 commits to Opentargets 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
high confidence
Implemented
Opentargets MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies 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 Opentargets 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
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-08-13
Activity Went Stale
No commits for 90 days

Maintain Opentargets MCP?

For maintainers

HVTrust scores Opentargets 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.

Reputation Timeline

Signal history
Rank 23Listed 2HVTrust 2Stale 1Scorecard 1Delisted 1Grade 1Provenance 1MCP 1Surface 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
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 594 spots (#868 → #274)
2026-09-23
HVTrust Changed
HVTrust up 45.1pts (27.5 → 72.6)
2026-09-22
Newly Listed
First tracked at rank #868
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 10 spots (#679 → #689)
2026-09-11
Rank Moved
Rank dropped 12 spots (#652 → #664)
2026-09-09
Rank Moved
Rank dropped 12 spots (#634 → #646)
2026-09-08
Rank Moved
Rank dropped 12 spots (#622 → #634)
2026-09-07
Rank Moved
Rank dropped 43 spots (#579 → #622)
2026-09-05
Rank Moved
Rank dropped 73 spots (#500 → #573)
2026-09-04
Rank Moved
Rank dropped 31 spots (#469 → #500)
2026-09-03
Rank Moved
Rank dropped 22 spots (#447 → #469)
2026-09-02
Rank Moved
Rank dropped 13 spots (#434 → #447)
2026-09-01
Rank Moved
Rank dropped 14 spots (#420 → #434)
2026-08-31
Rank Moved
Rank dropped 34 spots (#386 → #420)
2026-08-30
Rank Moved
Rank rose 14 spots (#400 → #386)
2026-08-29
Rank Moved
Rank dropped 13 spots (#387 → #400)
2026-08-27
Rank Moved
Rank dropped 11 spots (#375 → #386)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-26
Rank Moved
Rank rose 87 spots (#462 → #375)
2026-08-26
HVTrust Changed
HVTrust up 9.5pts (50.1 → 59.6)
2026-08-24
Rank Moved
Rank dropped 16 spots (#446 → #462)
2026-08-22
Rank Moved
Rank rose 14 spots (#461 → #447)
2026-08-19
Rank Moved
Rank dropped 12 spots (#449 → #461)
2026-08-17
Rank Moved
Rank rose 11 spots (#459 → #448)
2026-08-13
Activity Went Stale
No commits for 90 days
2026-08-13
Rank Moved
Rank dropped 14 spots (#433 → #447)
2026-08-12
Rank Moved
Rank rose 13 spots (#446 → #433)
2026-08-10
Rank Moved
Rank dropped 18 spots (#425 → #443)
2026-08-08
Newly Listed
First tracked at rank #424

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/opentargets-mcp.svg)](https://hvtracker.net/agents/opentargets-mcp)
HTML:
<a href="https://hvtracker.net/agents/opentargets-mcp"><img src="https://hvtracker.net/badge/opentargets-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