@blockrun/mcp
BlockRun MCP Server - Give your AI agent web search, deep research, prediction markets, crypto data, X/Twitter intelligence. Paid via x402 micropayments.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rpc-websockets | AI (phantom-deps): Solana/crypto MCP server; rpc-websockets is a transitive/indirect dep used via @solana/web3.js internals. | ai | |
| phantom-deps | phantom-dep:@solana/web3.js | AI (phantom-deps): Crypto-focused package; Solana deps referenced in config/bundled output, not direct imports. | ai | |
| phantom-deps | phantom-dep:@anthropic-ai/sdk | AI (phantom-deps): AI/LLM MCP server; Anthropic SDK likely used indirectly via @blockrun/llm abstraction layer. | ai | |
| phantom-deps | phantom-dep:@solana/spl-token | AI (phantom-deps): Crypto-focused package; SPL token dep consistent with Solana crypto data features. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @blockrun/mcp is unrelated to yup; edit-distance match is a false positive for this package. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 0.32.9 | 15 / 6 | |
| 0.32.8 | 15 / 6 | |
| 0.32.7 | 15 / 6 | |
| 0.32.6 | 15 / 6 | |
| 0.32.5 | 15 / 6 | |
| 0.32.4 | 15 / 6 | |
| 0.32.3 | 15 / 6 | |
| 0.32.2 | 15 / 6 | |
| 0.32.1 | 15 / 6 | |
| 0.32.0 | 15 / 6 | |
| 0.31.6 | 15 / 6 | |
| 0.31.5 | 15 / 5 | |
| 0.31.4 | 15 / 5 | |
| 0.31.3 | 15 / 5 | |
| 0.31.2 | 15 / 5 | |
| 0.31.1 | 15 / 5 | |
| 0.31.0 | 15 / 5 | |
| 0.30.10 | 15 / 5 | |
| 0.30.9 | 15 / 5 | |
| 0.30.8 | 15 / 5 | |
| 0.30.7 | 15 / 5 | |
| 0.30.6 | 15 / 5 | |
| 0.30.5 | 15 / 5 | |
| 0.30.4 | 15 / 5 | |
| 0.30.3 | 15 / 5 | |
| 0.30.2 | 15 / 5 | |
| 0.30.1 | 15 / 5 | |
| 0.30.0 | 15 / 5 | |
| 0.28.0 | 10 / 5 | |
| 0.26.0 | 10 / 5 | |
| 0.25.3 | 10 / 5 | |
| 0.25.2 | 10 / 5 | |
| 0.25.1 | 10 / 5 | |
| 0.25.0 | 10 / 5 | |
| 0.24.3 | 10 / 5 | |
| 0.24.2 | 10 / 5 | |
| 0.24.1 | 10 / 5 | |
| 0.24.0 | 10 / 5 | |
| 0.23.2 | 10 / 5 | |
| 0.23.1 | 10 / 5 | |
| 0.23.0 | 10 / 5 | |
| 0.22.3 | 11 / 5 | |
| 0.22.2 | 11 / 5 | |
| 0.22.1 | 11 / 5 | |
| 0.22.0 | 11 / 5 | |
| 0.21.5 | 11 / 5 | |
| 0.21.4 | 11 / 5 | |
| 0.21.3 | 10 / 5 | |
| 0.21.2 | 8 / 5 | |
| 0.21.1 | 8 / 5 | |
| 0.21.0 | 8 / 5 |
v0.32.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.