updated 2026-11-10 04:07 UTC

DexPaprika

Repository Website

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.9 / 10
Provenance None
Signed commits 66%
Last push 5d ago
Compare DexPaprika

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: DexPaprika scores 54.7/100 (Grade C), ranked #858 of 1374 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.9/10; 66% of recent commits are signed; last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How DexPaprika 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 DexPaprika 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/coinpaprika/dexpaprika-mcp, MIT, last pushed 2026-11-05. 66% 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.9/10 (scanned Oct 16, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    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 10

  3. Published packages None

    No registry package. DexPaprika 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-08-29 OSSF Scorecard: 4.9/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 DexPaprika’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 DexPaprika compares in MCP Servers

  1. #473 Ris MCP Ts 54.8 +0.1
  2. #474 Autotask 54.7 ±0
  3. #475 DexPaprika 54.7 this agent
  4. #476 Maven Tools MCP 54.7 ±0
  5. #477 Pgedge Postgres MCP 54.6 −0.1

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

Where the 54.7 comes from

HVTrust dimensions vs the MCP Servers average

54.7 / 100 · 100.0% confidence

DexPaprika MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.4 / 25
1.4 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
12.7 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
15.8 / 20
3.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.0 / 20
2.6 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-05
Rank Moved
Rank rose 89 spots (#937 → #848)
2026-11-01
Rank Moved
Rank dropped 39 spots (#892 → #931)
2026-10-29
Rank Moved
Rank dropped 13 spots (#867 → #880)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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
View MCP Servers Report missing data
56.8
Activity sub-score · out of 100
#475
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 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-11-10 04:07 UTC · Repo last pushed 5 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
118
Forks
30
Last Push
2026-11-05
5 days ago
Commits (4 wk)
10
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #858

Analysis

Activity Inputs

56.8 / 100
StarsRepository reach
12.5 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
13.0 / 25
CommunityFork signal
6.9 / 20

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.9/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 5 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?
66% 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
Rank 36HVTrust 2Grade 2Scorecard 1Score 1Delisted 1Listed 1MCP 1
2026-11-05
Rank Moved
Rank rose 89 spots (#937 → #848)
2026-11-01
Rank Moved
Rank dropped 39 spots (#892 → #931)
2026-10-29
Rank Moved
Rank dropped 13 spots (#867 → #880)
2026-10-28
Rank Moved
Rank dropped 19 spots (#848 → #867)
2026-10-26
Rank Moved
Rank dropped 11 spots (#838 → #849)
2026-10-21
Rank Moved
Rank rose 31 spots (#856 → #825)
2026-10-16
Rank Moved
Rank rose 73 spots (#929 → #856)
2026-10-12
Rank Moved
Rank rose 78 spots (#991 → #913)
2026-10-11
Rank Moved
Rank dropped 12 spots (#979 → #991)
2026-10-09
Rank Moved
Rank dropped 19 spots (#951 → #970)
2026-10-08
Rank Moved
Rank rose 10 spots (#961 → #951)
2026-09-30
Rank Moved
Rank dropped 12 spots (#943 → #955)
2026-09-28
Rank Moved
Rank rose 19 spots (#961 → #942)
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)
GitHub → Website →

Embed Badge Badge guide for maintainers →

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