Is MCPfinder - MCP Server Discovery safe to use?

MCPfinder - MCP Server Discovery has an HVTrust score of 52.6/100 (Grade C), ranked #863 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCPfinder - MCP Server Discovery?

MCPfinder - MCP Server Discovery scores 52.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

MCPfinder - MCP Server Discovery

mcpfinder/mcpfinder

MCP server that finds MCP servers. Discovers, evaluates, and installs 25K+ MCP servers across Official Registry, Glama, and Smithery for any AI client (Claude, Cursor, Cline, Windsurf).

MCP Servers JavaScript Listed AGPL-3.0

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

OSSF Scorecard 3.7 / 10

Provenance None

Signed commits 4%

Last push 17d ago

Compare MCPfinder - MCP Server Discovery

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCPfinder - MCP Server Discovery scores 52.6/100 (Grade C), ranked #863 of 1325 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 3.7/10; 4% of recent commits are signed; last pushed 2026-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCPfinder - MCP Server Discovery compares in MCP Servers

#487 Pulsemcp MCP Servers 52.8 +0.2
#488 GPU MCP Server 52.6 ±0
#489 MCPfinder - MCP Server Discovery 52.6 this agent
#490 SunoMCP 52.5 −0.1
#491 Longbridge MCP 52.5 −0.1

Bars show each HVTrust score; the tick marks MCPfinder - MCP Server Discovery’s 52.6.

Where the 52.6 comes from

HVTrust dimensions vs the MCP Servers average

52.6 / 100 · 100.0% confidence

MCPfinder - MCP Server Discovery MCP Servers average (775 agents)

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

4.8 / 25

5.5 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.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

14.9 / 20

2.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.5 / 20

1.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-26

Rank Moved

Rank dropped 10 spots (#853 → #863)

2026-09-25

Rank Moved

Rank dropped 18 spots (#835 → #853)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/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 MCPfinder - MCP Server Discovery View MCP Servers Report missing data

45.3

Activity sub-score · out of 100

#489

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 C 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-09

17 days ago

Commits (4 wk)

Downloads (7d)

132

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼10

was #853

Analysis

Activity Inputs

45.3 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

22.6 / 25

ActivityRecent commits

12.5 / 25

CommunityFork signal

3.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MCPfinder - MCP Server Discovery

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

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

Does MCPfinder - MCP Server Discovery have an OpenSSF Scorecard?

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

Maintained. Last push was 17 days ago.

What license does MCPfinder - MCP Server Discovery use?

MCPfinder - MCP Server Discovery ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCPfinder - MCP Server Discovery's commits signed?

4% of the last 100 commits to MCPfinder - MCP Server Discovery 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

MCPfinder - MCP Server Discovery 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.

Postgres

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 MCPfinder - MCP Server Discovery'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: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCPfinder - MCP Server Discovery?

For maintainers

HVTrust scores MCPfinder - MCP Server Discovery 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-26

Rank Moved

Rank dropped 10 spots (#853 → #863)

2026-09-25

Rank Moved

Rank dropped 18 spots (#835 → #853)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 185 spots (#1012 → #827)

2026-09-23

HVTrust Changed

HVTrust up 28.9pts (24.7 → 53.6)

2026-09-22

Newly Listed

First tracked at rank #1012

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 11 spots (#809 → #820)

2026-09-12

Rank Moved

Rank dropped 15 spots (#778 → #793)

2026-09-10

Rank Moved

Rank dropped 50 spots (#720 → #770)

2026-09-09

Rank Moved

Rank rose 38 spots (#758 → #720)

2026-09-07

Rank Moved

Rank dropped 68 spots (#683 → #751)

2026-09-06

Rank Moved

Rank dropped 13 spots (#670 → #683)

2026-09-05

Rank Moved

Rank dropped 74 spots (#596 → #670)

2026-09-04

Rank Moved

Rank dropped 54 spots (#542 → #596)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 504 spots (#1046 → #542)

2026-09-03

HVTrust Changed

HVTrust up 19.7pts (36.9 → 56.6)

2026-09-02

Rank Moved

Rank dropped 45 spots (#1001 → #1046)

2026-09-01

Rank Moved

Rank dropped 44 spots (#957 → #1001)

2026-08-31

Rank Moved

Rank dropped 34 spots (#923 → #957)

2026-08-30

Rank Moved

Rank dropped 43 spots (#880 → #923)

2026-08-29

Rank Moved

Rank dropped 48 spots (#832 → #880)

2026-08-28

Rank Moved

Rank dropped 25 spots (#807 → #832)

2026-08-27

Rank Moved

Rank dropped 15 spots (#792 → #807)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-26

Rank Moved

Rank rose 343 spots (#1135 → #792)

2026-08-26

HVTrust Changed

HVTrust up 17.5pts (19.0 → 36.5)

2026-08-26

Activity Score Changed

Activity score up 9pts (38 → 46)

2026-08-24

Rank Moved

Rank dropped 11 spots (#1122 → #1133)

2026-08-20

Rank Moved

Rank rose 74 spots (#1201 → #1127)

2026-08-20

Activity Score Changed

Activity score up 11pts (27 → 38)

2026-08-16

Rank Moved

Rank dropped 29 spots (#1175 → #1204)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1103 → #1173)

2026-08-08

Newly Listed

First tracked at rank #1098

GitHub → npm: @mcpfinder/server

Embed Badge Badge guide for maintainers →

For maintainers

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