updated 2026-10-16 16:07 UTC

MCPfinder - MCP Server Discovery

Repository Website

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? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 16%
Last push today
Advisories None known
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 56.0/100 (Grade C), ranked #808 of 1378 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; 16% of recent commits are signed; no published advisory affects its latest release (@mcpfinder/server); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCPfinder - MCP Server Discovery 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 MCPfinder - MCP Server Discovery 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/mcpfinder/mcpfinder, AGPL-3.0, last pushed 2026-10-16. 16% 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 3.7/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  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: @mcpfinder/server 1.5.0. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 4.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 MCPfinder - MCP Server Discovery’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 MCPfinder - MCP Server Discovery compares in MCP Servers

  1. #434 Fr24api MCP 56.1 +0.1
  2. #435 Ros2 MCP 56.0 ±0
  3. #436 MCPfinder - MCP Server Discovery 56.0 this agent
  4. #437 Git MCP Server 56.0 ±0
  5. #438 Greptimedb MCP Server 55.8 −0.2

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

Where the 56.0 comes from

HVTrust dimensions vs the MCP Servers average

56.0 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.4 / 25
5.1 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
11.6 / 17
0.7 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.6 / 20
5.3 above avg 12.3
AdoptionLog-scaled stars · package downloads
5.6 / 20
1.8 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-12
Rank Moved
Rank rose 13 spots (#827 → #814)
2026-10-11
Rank Moved
Rank dropped 10 spots (#817 → #827)
2026-10-10
Rank Moved
Rank dropped 17 spots (#800 → #817)
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
52.8
Activity sub-score · out of 100
#436
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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
13
Forks
4
Last Push
2026-10-16
today
Commits (4 wk)
25
Downloads (7d)
142
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▲5
was #813

Analysis

Activity Inputs

52.8 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
17.6 / 25
CommunityFork signal
3.3 / 20

Common questions about MCPfinder - MCP Server Discovery

MCPfinder - MCP Server Discovery 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 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?
Actively maintained. The repository was pushed to within the last 1 day(s).
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?
16% 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.
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
Rank 32Score 4HVTrust 4Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-12
Rank Moved
Rank rose 13 spots (#827 → #814)
2026-10-11
Rank Moved
Rank dropped 10 spots (#817 → #827)
2026-10-10
Rank Moved
Rank dropped 17 spots (#800 → #817)
2026-10-08
Rank Moved
Rank rose 24 spots (#822 → #798)
2026-10-07
Rank Moved
Rank dropped 12 spots (#810 → #822)
2026-10-03
Rank Moved
Rank rose 13 spots (#821 → #808)
2026-10-01
Rank Moved
Rank rose 110 spots (#935 → #825)
2026-10-01
HVTrust Changed
HVTrust up 3.4pts (50.7 → 54.1)
2026-10-01
Activity Score Changed
Activity score up 9pts (40 → 49)
2026-09-30
Rank Moved
Rank dropped 13 spots (#922 → #935)
2026-09-26
Rank Moved
Rank dropped 57 spots (#853 → #910)
2026-09-26
Activity Score Changed
Activity score down 7pts (47 → 40)
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 → Website → npm: @mcpfinder/server

Embed Badge Badge guide for maintainers →

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