Tracked packageView full profile for alchemy-mcp-server

MCPSafe.io

Security pre-install checks for MCP servers.

Mostly safe — a couple of notes worth reading.

Compare to another server

github · alchemy-mcp-serverHEAD

Item: alchemy-mcp-server
Rating: 4
Author: MCPSafe

Scanned 5/3/2026, 7:15:25 PM·Cached result·Fast Scan·45 rules·How we decide ↗

AIVSS Score

2.3/ 10

Low

Severity Breakdown

critical

high

medium

low

MCP Server Information

Packagealchemy-mcp-server

VersionHEAD

SourceGITHUB

LicenseMIT

Publisheralchemyplatform

Package age1y 1m

Stars83

Downloads/wk—

Dependencies0

Repositoryhttps://github.com/alchemyplatform/alchemy-mcp-server

Findings

7 of 7 findings

medium (7)

7 findings

medium (7)

AIVSS 2.3CVSS 3.5

Package declares an install-time hook (npm postinstall/preinstall/prepare, setup.py cmdclass override, custom setuptools install class, or non-default pyproject build-backend). Anyone installing this package runs the hook. Confirm the hook is necessary and review its contents; prefer shipping a plain library without install-time execution.

Evidence

},
  "scripts": {
    "build": "tsc && shx chmod +x dist/*.js",
    "prepare": "husky",
    "watch": "tsc --watch",
    "inspector": "npx @modelcontextprotocol/inspector node dist/index.js",
    "test": "npx tsx --test tests/*.test.ts",

Remediation

Prefer libraries that do not require install-time code execution: - Drop `postinstall`/`preinstall`/`prepare` scripts if the work can happen at runtime or build-time instead. - Ship pre-built native binaries rather than compiling via a custom `cmdclass` or `build_ext` override. - For Dockerfiles: replace `RUN curl … | sh` with a pinned download + checksum verification + explicit `RUN` of a named script. - If the hook is unavoidable, document exactly what it does so downstream reviewers

Report false positive

AIVSS 2.3CVSS 3.5

GitHub Actions `uses:` reference is not pinned to a 40-character commit SHA. Tags (`@v4`) and branches (`@main`) are mutable — a compromised maintainer or a tag rewrite can substitute malicious code into your CI pipeline silently. Pin to a SHA: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab`. For readability, include the version as a trailing comment: `# v4.1.1`. Tools like `pinact` / `ratchet` automate this. Allowed unpinned forms (excluded by the rule): - Local actions `.

Evidence

validate-changesets:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - name: Validate changeset files have version bump
        run: |
          invalid_files=""

Remediation

Pin every `uses:` to a 40-character commit SHA. Trailing comment with the version helps reviewers: `uses: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab # v4.1.1` Automate the migration with `pinact` (https://github.com/suzuki-shunsuke/pinact) or `ratchet` (https://github.com/sethvargo/ratchet). Add a `pinact run --check` pre-commit hook so future PRs stay pinned. Re-pin when the action releases a new version — Dependabot can do this automatically with `version-update-strategy: inc

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - uses: actions/checkout@v6
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
      - uses: actions/setup-node@v6
        with:
          node-version: 24
          cache: pnpm

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
      - uses: actions/setup-node@v6
        with:

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

with:
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}
      - uses: actions/checkout@v6
        with:
          token: ${{ steps.app-token.outputs.token }}
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - name: Generate GitHub App token
        id: app-token
        uses: actions/create-github-app-token@v2
        with:
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

with:
          token: ${{ steps.app-token.outputs.token }}
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
      - uses: actions/setup-node@v6
        with:
          node-version: 24
          cache: pnpm

Remediation

Report false positive

LLM summary— alchemy-mcp-server:HEAD

This package receives a B grade with a safety score of 88/100 but has a concerning AIVSS score of 2.2/10, indicating potential AI/LLM-specific vulnerabilities. All seven medium-severity findings relate to server configuration issues, which could expose the MCP server to misuse or information disclosure if not properly hardened in your deployment environment. While no critical or high-severity issues were detected, you should review the configuration recommendations before production use.

Signal scores

Static100

CVE check100

Publisher identity50

Permissions100

Supply chain44

Typosquat100

Package health85

Community82

Secrets & exfil100

Injection risks100

Destructive ops100

LLM judge panel

CVE check

No known CVEs found for this package or its dependencies.

Community trust

No community reports

Security policy: Not found
Advisories: 0

Scan details

Total findings: 7
Affected tools: 0 / 1
Scan type: Fast Scan
Rules run: 45
LLM consensus score: N/A
Scanned: 107d ago
Source: GITHUB

MCP Server Information

Source: GITHUB
Package: alchemy-mcp-server
Version: HEAD
License: MIT
Publisher: alchemyplatform
Verified: No
Account age: 7y 0m
Added: 1y 1m ago
Versions: 83
Repository: https://github.com/alchemyplatform/alchemy-mcp-server
Ecosystem: GitHub
Stars: 83
Forks: 30
Open issues: 7
Dependencies: 0

AIVSS Score

2.3/ 10Low

Internal score: 88/100

Severity breakdown

Scan Details

Total findings7

Affected tools0 / 1

Scanned107d ago

Scan modeFAST

SourceGITHUB

Scan IDpubfastb9b99490d29d602edc48

Want deeper analysis?

Fast scan found 7 findings using rule-based analysis. Upgrade for LLM consensus across 5 judges, AI-generated remediation, and cross-file taint analysis.

View plans Scan another package

Building your own MCP server?

Run this exact engine on your private repo — before users see it on /scan.

Same rules, same LLM judges, same grade. Private scans stay isolated to your account and never appear in the public registry. Required for code your team hasn’t shipped yet.

See plans with Private scans How private scans stay private

7 of 7 findings

medium (7)

7 findings

medium (7)

AIVSS 2.3CVSS 3.5

Evidence

},
  "scripts": {
    "build": "tsc && shx chmod +x dist/*.js",
    "prepare": "husky",
    "watch": "tsc --watch",
    "inspector": "npx @modelcontextprotocol/inspector node dist/index.js",
    "test": "npx tsx --test tests/*.test.ts",

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

validate-changesets:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - name: Validate changeset files have version bump
        run: |
          invalid_files=""

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - uses: actions/checkout@v6
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
      - uses: actions/setup-node@v6
        with:
          node-version: 24
          cache: pnpm

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
      - uses: actions/setup-node@v6
        with:

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

with:
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}
      - uses: actions/checkout@v6
        with:
          token: ${{ steps.app-token.outputs.token }}
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

steps:
      - name: Generate GitHub App token
        id: app-token
        uses: actions/create-github-app-token@v2
        with:
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}

Remediation

Report false positive

AIVSS 2.3CVSS 3.5

Evidence

with:
          token: ${{ steps.app-token.outputs.token }}
      - uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
      - uses: actions/setup-node@v6
        with:
          node-version: 24
          cache: pnpm

Remediation

Report false positive

29	},
30	"scripts": {
31	"build": "tsc && shx chmod +x dist/*.js",
32	"prepare": "husky",
33	"watch": "tsc --watch",
34	"inspector": "npx @modelcontextprotocol/inspector node dist/index.js",
35	"test": "npx tsx --test tests/*.test.ts",

11	validate-changesets:
12	runs-on: ubuntu-latest
13	steps:
14	- uses: actions/checkout@v6
15	- name: Validate changeset files have version bump
16	run: \|
17	invalid_files=""

38	steps:
39	- uses: actions/checkout@v6
40	- uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
41	- uses: actions/setup-node@v6
42	with:
43	node-version: 24
44	cache: pnpm

36	check:
37	runs-on: ubuntu-latest
38	steps:
39	- uses: actions/checkout@v6
40	- uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
41	- uses: actions/setup-node@v6
42	with:

27	with:
28	app-id: ${{ vars.APP_ID }}
29	private-key: ${{ secrets.APP_PRIVATE_KEY }}
30	- uses: actions/checkout@v6
31	with:
32	token: ${{ steps.app-token.outputs.token }}
33	- uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0

23	steps:
24	- name: Generate GitHub App token
25	id: app-token
26	uses: actions/create-github-app-token@v2
27	with:
28	app-id: ${{ vars.APP_ID }}
29	private-key: ${{ secrets.APP_PRIVATE_KEY }}