Is Linkup MCP Server safe to use?

Linkup MCP Server has an HVTrust score of 45.6/100 (Grade D), ranked #1047 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Linkup MCP Server?

Linkup MCP Server scores 45.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 29 GitHub stars and is categorized under MCP Servers.

Linkup MCP Server

LinkupPlatform/linkup-mcp-server

Linkup MCP server for web search and fetching web content

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.8 / 10

Provenance None

Signed commits 26%

Last push 11d ago

Compare Linkup MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Linkup MCP Server scores 45.6/100 (Grade D), ranked #1047 of 1325 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.8/10; 26% of recent commits are signed; last pushed 2026-09-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Linkup MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Linkup MCP Server’s 45.6.

Where the 45.6 comes from

HVTrust dimensions vs the MCP Servers average

45.6 / 100 · 100.0% confidence

Linkup MCP Server MCP Servers average (775 agents)

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

6.1 / 25

4.2 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.7 / 17

0.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.5 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

3.5 / 20

3.7 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 dropped 456 spots (#580 → #1036)

2026-09-23

HVTrust Changed

HVTrust up 10.8pts (35.0 → 45.8)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/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.

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

39.6

Activity sub-score · out of 100

#613

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-15

11 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #1050

Analysis

Activity Inputs

39.6 / 100

StarsRepository reach

8.9 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

3.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.8 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

26%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 8

CII-Best-Practices 0

Code-Review 1

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Linkup MCP Server

Public trust evidence for Linkup MCP Server 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 Linkup MCP Server publish package provenance?

No published build provenance is currently detected for Linkup MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Linkup MCP Server have an OpenSSF Scorecard?

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

Maintained. Last push was 11 days ago.

What license does Linkup MCP Server use?

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

Are Linkup MCP Server's commits signed?

26% of the last 100 commits to Linkup 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

high confidence

Implemented

Linkup 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

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 Linkup 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-15

Activity Resumed

Activity resumed

2026-09-07

Activity Went Stale

No commits for 90 days

Maintain Linkup MCP Server?

For maintainers

HVTrust scores Linkup 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

Rank Moved

Rank dropped 456 spots (#580 → #1036)

2026-09-23

HVTrust Changed

HVTrust up 10.8pts (35.0 → 45.8)

2026-09-22

Newly Listed

First tracked at rank #580

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank dropped 12 spots (#1022 → #1034)

2026-09-15

Activity Resumed

Activity resumed

2026-09-15

Rank Moved

Rank rose 163 spots (#1185 → #1022)

2026-09-15

HVTrust Changed

HVTrust up 7.7pts (38.6 → 46.3)

2026-09-15

Activity Score Changed

Activity score up 17pts (24 → 41)

2026-09-13

Scorecard Added

OSSF Scorecard: 3.8/10

2026-09-13

Rank Moved

Rank rose 142 spots (#1325 → #1183)

2026-09-13

HVTrust Changed

HVTrust up 22.7pts (16.0 → 38.7)

2026-09-07

Activity Went Stale

No commits for 90 days

2026-09-02

Rank Moved

Rank dropped 12 spots (#1294 → #1306)

2026-08-29

Rank Moved

Rank dropped 11 spots (#1264 → #1275)

2026-08-26

Rank Moved

Rank dropped 30 spots (#1218 → #1248)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1186 → #1212)

2026-08-10

Rank Moved

Rank dropped 72 spots (#1111 → #1183)

2026-08-08

Newly Listed

First tracked at rank #1107

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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