updated 2026-10-16 20:06 UTC

Linkup MCP Server

Repository Website

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 4.1 / 10
Provenance None
Signed commits 35%
Last push today
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 47.4/100 (Grade D), ranked #1070 of 1378 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 4.1/10; 35% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Linkup MCP Server 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 Linkup MCP Server 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/LinkupPlatform/linkup-mcp-server, MIT, last pushed 2026-10-16. 35% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review2
    • Branch Protection5
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies7
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 3
    Packaging -1
    Pinned-Dependencies 7
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Linkup MCP Server 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-09-13 OSSF Scorecard: 3.8/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 Linkup MCP Server’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 Linkup MCP Server compares in MCP Servers

  1. #609 Reddit Research MCP 47.5 +0.1
  2. #610 Temporal Cortex Calendar MCP 47.4 ±0
  3. #611 Linkup MCP Server 47.4 this agent
  4. #612 CVE MCP Server 47.4 ±0
  5. #613 Zapier 47.3 −0.1

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

Where the 47.4 comes from

HVTrust dimensions vs the MCP Servers average

47.4 / 100 · 100.0% confidence

Linkup MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.9 / 25
3.6 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.2 / 20
0.9 above avg 12.3
AdoptionLog-scaled stars · package downloads
3.5 / 20
3.9 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 13 spots (#1059 → #1072)
2026-10-14
Rank Moved
Rank dropped 17 spots (#1042 → #1059)
2026-10-09
Rank Moved
Rank rose 18 spots (#1031 → #1013)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/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
45.0
Activity sub-score · out of 100
#611
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-10-16 20:06 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
29
Forks
5
Last Push
2026-10-16
today
Commits (4 wk)
3?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▲2
was #1072

Analysis

Activity Inputs

45.0 / 100
StarsRepository reach
8.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
3.6 / 20

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 4.1/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?
Actively maintained. The repository was pushed to within the last 1 day(s).
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?
34% 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
Rank 15HVTrust 3Listed 2Score 2Stale 1Scorecard 1Fresh 1Delisted 1MCP 1
2026-10-15
Rank Moved
Rank dropped 13 spots (#1059 → #1072)
2026-10-14
Rank Moved
Rank dropped 17 spots (#1042 → #1059)
2026-10-09
Rank Moved
Rank rose 18 spots (#1031 → #1013)
2026-10-03
Rank Moved
Rank rose 33 spots (#1047 → #1014)
2026-10-01
Rank Moved
Rank rose 39 spots (#1078 → #1039)
2026-10-01
Activity Score Changed
Activity score up 7pts (39 → 46)
2026-09-27
Rank Moved
Rank dropped 15 spots (#1049 → #1064)
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 → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 47.4 Grade D
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.4 · Raw JSON