updated 2026-11-10 04:07 UTC

Driflyte MCP Server

Repository

The Driflyte MCP Server exposes tools that allow AI assistants to query and retrieve topic-specific knowledge from recursively crawled and indexed web pages.

MCP Servers TypeScript Needs review MIT

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

OSSF Scorecard 2.3 / 10
Provenance None
Signed commits 9%
Last push 404d ago
Advisories None known
Compare Driflyte MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Driflyte MCP Server scores 26.1/100 (Grade D), ranked #1359 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.3/10; 9% of recent commits are signed; no published advisory affects its latest release (@driflyte/mcp-server); last pushed 2025-10-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Driflyte 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
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-10-02)

Chain of custody

Scanners check what the code says. This traces who ships Driflyte MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/serkan-ozal/driflyte-mcp-server, MIT, last pushed 2025-10-02. 9% 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 2.3/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    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 -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @driflyte/mcp-server 0.1.15. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 2.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Driflyte 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 Driflyte MCP Server compares in MCP Servers

  1. #773 MCP Toolbox for Databases 26.8 +0.7
  2. #774 MCP Apple Notes 26.7 +0.6
  3. #775 Driflyte MCP Server 26.1 this agent
  4. #776 MCP Skills Server 25.2 −0.9
  5. #777 HAL 24.0 −2.1

Bars show each HVTrust score; the tick marks Driflyte MCP Server’s 26.1.

Where the 26.1 comes from

HVTrust dimensions vs the MCP Servers average

26.1 / 100 · 100.0% confidence

Driflyte MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.3 / 25
7.5 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
10.5 / 17
1.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.5 / 20
2.1 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.3/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 404 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-10-02)
Compare with another agent
View MCP Servers Report missing data
10.4
Activity sub-score · out of 100
#775
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 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-11-10 04:07 UTC · Repo last pushed 404 days ago — may be stale

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
11
Forks
6
Last Push
2025-10-02
404 days ago
Commits (4 wk)
0
Downloads (7d)
141
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #1359

Analysis

Activity Inputs

10.4 / 100
StarsRepository reach
6.5 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.9 / 20

Common questions about Driflyte MCP Server

Public trust evidence for Driflyte 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 Driflyte MCP Server publish package provenance?
No published build provenance is currently detected for Driflyte 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 Driflyte MCP Server have an OpenSSF Scorecard?
Driflyte MCP Server has an OpenSSF Scorecard score of 2.3/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 Driflyte MCP Server actively maintained?
Stale. The repository has not been pushed to in 404 days. Consider whether the project is still being maintained.
What license does Driflyte MCP Server use?
Driflyte MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Driflyte MCP Server's commits signed?
9% of the last 100 commits to Driflyte 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
Driflyte MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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 Driflyte 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

Maintain Driflyte MCP Server?

For maintainers

HVTrust scores Driflyte 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 10HVTrust 4Scorecard 1Delisted 1Listed 1MCP 1Warning Issued 1
2026-10-09
Rank Moved
Rank dropped 13 spots (#1324 → #1337)
2026-10-03
Rank Moved
Rank dropped 87 spots (#1236 → #1323)
2026-10-03
HVTrust Changed
HVTrust down 10.1pts (36.6 → 26.5)
2026-10-02
Warning Issued
Warning: eligibility issues detected
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 96 spots (#1307 → #1211)
2026-09-23
HVTrust Changed
HVTrust up 24.6pts (12.4 → 37.0)
2026-09-22
Newly Listed
First tracked at rank #1307
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 12 spots (#1183 → #1195)
2026-09-08
Rank Moved
Rank dropped 12 spots (#1171 → #1183)
2026-09-07
Rank Moved
Rank rose 117 spots (#1288 → #1171)
2026-09-07
HVTrust Changed
HVTrust up 12.9pts (24.4 → 37.3)
2026-09-06
Rank Moved
Rank dropped 11 spots (#1277 → #1288)
2026-09-05
Scorecard Added
OSSF Scorecard: 2.5/10
2026-09-05
Rank Moved
Rank rose 40 spots (#1317 → #1277)
2026-09-05
HVTrust Changed
HVTrust up 9.4pts (15.0 → 24.4)
2026-08-26
Rank Moved
Rank dropped 19 spots (#1265 → #1284)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1243 → #1268)
GitHub → npm: @driflyte/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 26.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/driflyte-mcp-server.svg)](https://hvtracker.net/agents/driflyte-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/driflyte-mcp-server"><img src="https://hvtracker.net/badge/driflyte-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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