Is Blockrun MCP safe to use?

Blockrun MCP has an HVTrust score of 81.7/100 (Grade A), ranked #154 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Blockrun MCP?

Blockrun MCP scores 81.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 390 GitHub stars and is categorized under MCP Servers.

Blockrun MCP

Repository by BlockRunAI

Live data for AI agents — search, research, markets, crypto, X/Twitter. Pay-per-call via x402 micropayments.

MCP Servers TypeScript Listed MIT

Is Blockrun MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.3 / 10

Provenance Attested

Signed commits 68%

Last push yesterday

Advisories None known

Compare Blockrun MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Blockrun MCP scores 81.7/100 (Grade A), ranked #154 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.3/10; 68% of recent commits are signed; no published advisory affects its latest release (@blockrun/mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Blockrun 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.

Raise the OSSF Scorecard from 5.3 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +6.3 → 88.0 A · #19 of 778
Sign every commit68% signed today +1.6 → 83.3 A · #53 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Blockrun MCP 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.

Source Partly signed

github.com/BlockRunAI/blockrun-mcp, MIT, last pushed 2026-11-09. 68% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.3/10 (scanned Nov 1, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm @blockrun/mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @blockrun/mcp 0.55.7. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-09-03 OSSF Scorecard: 5.3/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 Blockrun 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 Blockrun MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Blockrun MCP’s 81.7.

Where the 81.7 comes from

HVTrust dimensions vs the MCP Servers average

81.7 / 100 · 100.0% confidence

Blockrun MCP MCP Servers average (778 agents)

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

17.5 / 25

6.7 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

0.7 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

17.9 / 20

5.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

10.6 / 20

3.0 above avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-04

Rank Moved

Rank rose 15 spots (#156 → #141)

2026-11-01

Rank Moved

Rank dropped 17 spots (#152 → #169)

2026-10-27

Rank Moved

Rank dropped 16 spots (#128 → #144)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent View MCP Servers Report missing data

67.0

Activity sub-score · out of 100

#72

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 A 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-09-29 2026-11-10

Activity & Reach

Stars

390

Forks

Last Push

2026-11-09

yesterday

Commits (4 wk)

Downloads (7d)

1,831

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #150

Analysis

Activity Inputs

67.0 / 100

StarsRepository reach

15.6 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

18.8 / 25

CommunityFork signal

7.6 / 20

Common questions about Blockrun MCP

Public supply-chain signals for Blockrun MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Blockrun MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Blockrun MCP publish package provenance?

Yes. Blockrun MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Blockrun MCP have an OpenSSF Scorecard?

Blockrun MCP has an OpenSSF Scorecard score of 5.3/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 Blockrun MCP actively maintained?

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

What license does Blockrun MCP use?

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

Are Blockrun MCP's commits signed?

68% of the last 100 commits to Blockrun 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

Blockrun MCP 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.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Blockrun 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

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Blockrun MCP?

For maintainers

HVTrust scores Blockrun 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

2026-11-04

Rank Moved

Rank rose 15 spots (#156 → #141)

2026-11-01

Rank Moved

Rank dropped 17 spots (#152 → #169)

2026-10-27

Rank Moved

Rank dropped 16 spots (#128 → #144)

2026-10-26

Rank Moved

Rank rose 22 spots (#150 → #128)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 575 spots (#703 → #128)

2026-09-23

HVTrust Changed

HVTrust up 50.7pts (30.8 → 81.5)

2026-09-22

Newly Listed

First tracked at rank #703

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Grade Changed

Trust grade C → A

2026-09-05

Rank Moved

Rank rose 547 spots (#635 → #88)

2026-09-05

HVTrust Changed

HVTrust up 28.7pts (54.6 → 83.3)

2026-09-04

Rank Moved

Rank dropped 22 spots (#613 → #635)

2026-09-03

Scorecard Added

OSSF Scorecard: 5.3/10

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 175 spots (#788 → #613)

2026-09-03

HVTrust Changed

HVTrust up 7.4pts (47.2 → 54.6)

2026-09-02

Grade Changed

Trust grade B → D

2026-09-02

Rank Moved

Rank dropped 612 spots (#176 → #788)

2026-09-02

HVTrust Changed

HVTrust down 24.6pts (71.8 → 47.2)

2026-08-31

Grade Changed

Trust grade D → B

2026-08-31

Rank Moved

Rank rose 519 spots (#692 → #173)

2026-08-31

HVTrust Changed

HVTrust up 24.8pts (47.0 → 71.8)

2026-08-30

Grade Changed

Trust grade B → D

2026-08-30

Rank Moved

Rank dropped 528 spots (#164 → #692)

2026-08-30

HVTrust Changed

HVTrust down 24.4pts (71.4 → 47.0)

2026-08-26

Rank Moved

Rank dropped 20 spots (#134 → #154)

2026-08-24

Grade Changed

Trust grade D → B

2026-08-24

Rank Moved

Rank rose 365 spots (#499 → #134)

2026-08-24

HVTrust Changed

HVTrust up 24.5pts (46.7 → 71.2)

2026-08-22

Grade Changed

Trust grade B → D

2026-08-22

Rank Moved

Rank dropped 375 spots (#126 → #501)

2026-08-22

HVTrust Changed

HVTrust down 25.2pts (71.9 → 46.7)

2026-08-19

Grade Changed

Trust grade D → B

2026-08-19

Rank Moved

Rank rose 378 spots (#498 → #120)

2026-08-19

HVTrust Changed

HVTrust up 25.4pts (47.1 → 72.5)

2026-08-17

Grade Changed

Trust grade B → D

2026-08-17

Rank Moved

Rank dropped 377 spots (#122 → #499)

2026-08-17

HVTrust Changed

HVTrust down 25.1pts (72.1 → 47.0)

2026-08-13

Grade Changed

Trust grade D → B

2026-08-13

Rank Moved

Rank rose 374 spots (#487 → #113)

2026-08-13

HVTrust Changed

HVTrust up 25.5pts (47.2 → 72.7)

GitHub → npm: @blockrun/mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Blockrun MCP

How Blockrun MCP could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Blockrun MCP compares in MCP Servers

Where the 81.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Blockrun MCP

AI agent surface

Maintain Blockrun MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers