updated 2026-11-11 00:08 UTC

Sperax Crypto MCP

Repository

MCP server and plugin for Sperax Protocol – USDs, SPA, veSPA & Demeter on Arbitrum and BNB Chain. Listed on Anthropic's official MCP Registry.

MCP Servers TypeScript Listed MIT

Is Sperax Crypto MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.2 / 10
Provenance None
Signed commits 20%
Last push 52d ago
Compare Sperax Crypto MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Sperax Crypto MCP scores 38.2/100 (Grade D), ranked #1243 of 1387 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 2.2/10; 20% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Sperax Crypto MCP 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 Sperax Crypto MCP 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/Sperax/sperax-crypto-mcp, MIT, last pushed 2026-09-20. 20% 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.2/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages None

    No registry package. Sperax Crypto MCP 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-28 OSSF Scorecard: 2.2/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 Sperax Crypto MCP’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 Sperax Crypto MCP compares in MCP Servers

  1. #714 MCP Codebase Index 38.6 +0.4
  2. #715 Ui Annotator MCP 38.4 +0.2
  3. #716 Sperax Crypto MCP 38.2 this agent
  4. #717 Power Automate MCP Server by Flow Studio 38.1 −0.1
  5. #718 Weapp Agent MCP 38.1 −0.1

Bars show each HVTrust score; the tick marks Sperax Crypto MCP’s 38.2.

Where the 38.2 comes from

HVTrust dimensions vs the MCP Servers average

38.2 / 100 · 100.0% confidence

Sperax Crypto MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.8 / 25
7.0 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.4 / 17
1.9 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
8.5 / 20
3.8 below avg 12.3
AdoptionLog-scaled stars · package downloads
3.0 / 20
4.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-10-20
Rank Moved
Rank dropped 32 spots (#1191 → #1223)
2026-10-15
Rank Moved
Rank dropped 10 spots (#1175 → #1185)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.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.
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 52 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
28.1
Activity sub-score · out of 100
#716
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 →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 52 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
16
Forks
3
Last Push
2026-09-20
52 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1243

Analysis

Activity Inputs

28.1 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
17.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.8 / 20

Common questions about Sperax Crypto MCP

Public trust evidence for Sperax Crypto MCP 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 Sperax Crypto MCP publish package provenance?
No published build provenance is currently detected for Sperax Crypto MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Sperax Crypto MCP have an OpenSSF Scorecard?
Sperax Crypto MCP has an OpenSSF Scorecard score of 2.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 Sperax Crypto MCP actively maintained?
Slowing down. Last push was 52 days ago — keep an eye on whether activity resumes.
What license does Sperax Crypto MCP use?
Sperax Crypto MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Sperax Crypto MCP's commits signed?
20% of the last 100 commits to Sperax Crypto MCP 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
Sperax Crypto MCP 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
high confidence
Declared
Declared plugin/integration 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 Sperax Crypto MCP'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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Sperax Crypto MCP?

For maintainers

HVTrust scores Sperax Crypto MCP 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 22HVTrust 3Scorecard 1Score 1Delisted 1Listed 1MCP 1Surface 1
2026-10-20
Rank Moved
Rank dropped 32 spots (#1191 → #1223)
2026-10-15
Rank Moved
Rank dropped 10 spots (#1175 → #1185)
2026-10-09
Rank Moved
Rank dropped 12 spots (#1144 → #1156)
2026-09-28
Rank Moved
Rank rose 19 spots (#1130 → #1111)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 454 spots (#664 → #1118)
2026-09-23
HVTrust Changed
HVTrust up 10.7pts (31.6 → 42.3)
2026-09-22
Newly Listed
First tracked at rank #664
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 92 spots (#1214 → #1122)
2026-09-20
HVTrust Changed
HVTrust up 5.7pts (36.6 → 42.3)
2026-09-20
Activity Score Changed
Activity score up 14pts (25 → 39)
2026-09-09
Rank Moved
Rank dropped 12 spots (#1184 → #1196)
2026-09-08
Rank Moved
Rank dropped 17 spots (#1167 → #1184)
2026-09-07
Rank Moved
Rank dropped 14 spots (#1153 → #1167)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1139 → #1153)
2026-09-05
Rank Moved
Rank dropped 37 spots (#1102 → #1139)
2026-09-04
Rank Moved
Rank dropped 22 spots (#1080 → #1102)
2026-09-03
Rank Moved
Rank dropped 56 spots (#1024 → #1080)
2026-09-02
Rank Moved
Rank dropped 46 spots (#978 → #1024)
2026-09-01
Rank Moved
Rank dropped 44 spots (#934 → #978)
2026-08-31
Rank Moved
Rank dropped 31 spots (#903 → #934)
2026-08-30
Rank Moved
Rank dropped 40 spots (#863 → #903)
2026-08-29
Rank Moved
Rank dropped 47 spots (#816 → #863)
2026-08-28
Scorecard Added
OSSF Scorecard: 2.2/10
2026-08-28
Rank Moved
Rank rose 415 spots (#1231 → #816)
2026-08-28
HVTrust Changed
HVTrust up 20.5pts (17.6 → 38.1)
2026-08-27
Rank Moved
Rank dropped 10 spots (#1221 → #1231)
2026-08-26
Rank Moved
Rank dropped 35 spots (#1186 → #1221)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1157 → #1183)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 38.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/sperax-crypto-mcp.svg)](https://hvtracker.net/agents/sperax-crypto-mcp)
HTML:
<a href="https://hvtracker.net/agents/sperax-crypto-mcp"><img src="https://hvtracker.net/badge/sperax-crypto-mcp.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