Is DexPaprika safe to use?

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

What is the trust score for DexPaprika?

DexPaprika scores 49.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 42 GitHub stars and is categorized under MCP Servers.

DexPaprika

coinpaprika/dexpaprika-mcp

DexPaprika MCP server for real-time crypto token data, DEX trading activity, and DeFi analytics across multiple blockchains.

MCP Servers JavaScript Listed MIT

Is DexPaprika safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 60%

Last push yesterday

Compare DexPaprika

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: DexPaprika scores 49.1/100 (Grade D), ranked #960 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 4.2/10; 60% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How DexPaprika compares in MCP Servers

#553 Home Assistant Vibecode Agent 49.3 +0.2
#554 Bgg MCP 49.1 ±0
#555 DexPaprika 49.1 this agent
#556 CometChat Docs 49.0 −0.1
#557 MCP Slim Guard 49.0 −0.1

Bars show each HVTrust score; the tick marks DexPaprika’s 49.1.

Where the 49.1 comes from

HVTrust dimensions vs the MCP Servers average

49.1 / 100 · 100.0% confidence

DexPaprika MCP Servers average (775 agents)

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

8.2 / 25

2.1 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

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

1.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

3.9 / 20

3.3 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 423 spots (#544 → #967)

2026-09-23

HVTrust Changed

HVTrust up 11.4pts (37.4 → 48.8)

Maintainer Checklist

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

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

48.1

Activity sub-score · out of 100

#555

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-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #958

Analysis

Activity Inputs

48.1 / 100

StarsRepository reach

9.8 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

60%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 1

Common questions about DexPaprika

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

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

Does DexPaprika have an OpenSSF Scorecard?

DexPaprika has an OpenSSF Scorecard score of 4.2/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 DexPaprika actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does DexPaprika use?

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

Are DexPaprika's commits signed?

59% of the last 100 commits to DexPaprika 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

DexPaprika 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 DexPaprika'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 DexPaprika?

For maintainers

HVTrust scores DexPaprika 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 423 spots (#544 → #967)

2026-09-23

HVTrust Changed

HVTrust up 11.4pts (37.4 → 48.8)

2026-09-22

Newly Listed

First tracked at rank #544

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 15 spots (#949 → #964)

2026-09-18

Rank Moved

Rank dropped 16 spots (#935 → #951)

2026-09-15

Grade Changed

Trust grade C → D

2026-09-15

Rank Moved

Rank dropped 45 spots (#906 → #951)

2026-09-13

Rank Moved

Rank dropped 63 spots (#846 → #909)

2026-09-13

Activity Score Changed

Activity score down 6pts (51 → 45)

2026-09-12

Rank Moved

Rank rose 53 spots (#899 → #846)

2026-09-11

Rank Moved

Rank dropped 15 spots (#884 → #899)

2026-09-09

Rank Moved

Rank dropped 18 spots (#865 → #883)

2026-09-08

Rank Moved

Rank dropped 12 spots (#853 → #865)

2026-09-07

Rank Moved

Rank dropped 40 spots (#813 → #853)

2026-09-06

Rank Moved

Rank dropped 77 spots (#736 → #813)

2026-09-05

Rank Moved

Rank dropped 68 spots (#668 → #736)

2026-09-04

Rank Moved

Rank dropped 31 spots (#637 → #668)

2026-09-03

Rank Moved

Rank dropped 36 spots (#601 → #637)

2026-09-02

Rank Moved

Rank dropped 30 spots (#571 → #601)

2026-09-01

Rank Moved

Rank dropped 21 spots (#550 → #571)

2026-08-31

Rank Moved

Rank dropped 32 spots (#518 → #550)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.9/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 542 spots (#1061 → #519)

2026-08-29

HVTrust Changed

HVTrust up 31.3pts (23.2 → 54.5)

2026-08-28

Rank Moved

Rank dropped 36 spots (#1025 → #1061)

2026-08-27

Rank Moved

Rank dropped 27 spots (#998 → #1025)

2026-08-26

Rank Moved

Rank dropped 99 spots (#899 → #998)

2026-08-16

Rank Moved

Rank dropped 20 spots (#881 → #901)

2026-08-14

Rank Moved

Rank rose 20 spots (#904 → #884)

2026-08-12

Rank Moved

Rank rose 10 spots (#905 → #895)

2026-08-10

Rank Moved

Rank dropped 56 spots (#841 → #897)

2026-08-08

Newly Listed

First tracked at rank #835

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/dexpaprika.svg)](https://hvtracker.net/agents/dexpaprika)
            
HTML:
            <a href="https://hvtracker.net/agents/dexpaprika"><img src="https://hvtracker.net/badge/dexpaprika.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