Is Blockrun MCP safe to use?

Blockrun MCP has an HVTrust score of 71.9/100 (Grade B), ranked #120 of 1283 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 71.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 426 GitHub stars and is categorized under MCP Servers.

Blockrun MCP

BlockRunAI/blockrun-mcp

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

MCP Servers TypeScript Grade B Listed MIT

71.9/100

Rank #120 of 1283

Compare Blockrun MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-10 · 2d ago

Recent change

New

Is Blockrun MCP safe? Blockrun MCP scores 71.9/100 (Grade B), ranked #120 of 1283 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; no OSSF Scorecard result yet; 58% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#18 DaVinci Resolve MCP — 72.8 (B) → #19 Safari MCP — 71.9 (B) → #21 AWS MCP Servers — 71.7 (B) → #22 Sentry MCP — 71.5 (B) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-08

Newly Listed

First tracked at rank #105

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

70.9

Activity sub-score · out of 100

#20

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 B 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-08-11 2026-08-12

Activity & Reach

Stars

426

Forks

Last Push

2026-08-10

2 days ago

Commits (4 wk)

Downloads (7d)

2,420

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #119

Analysis

HVTrust Dimensions vs MCP Servers

71.9 / 100 · 100.0% confidence

Blockrun MCP MCP Servers average (761 agents)

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

10.4 / 25

5.4 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.0 / 20

6.6 above avg 12.4

AdoptionLog-scaled stars · package downloads

10.8 / 20

5.0 above avg 5.8

Activity Inputs

70.9 / 100

StarsRepository reach

15.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

22.4 / 25

CommunityFork signal

7.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

58%

of last 100 commits verified

Is Blockrun MCP safe?

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

No OpenSSF Scorecard data is currently published for Blockrun MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Blockrun MCP actively maintained?

Actively maintained. The repository was pushed to within the last 2 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?

57% 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

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium 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

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

Newly Listed

First tracked at rank #105

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON