# Presend dependency checks (remote · presend.pages.dev)

Check an npm/PyPI package before an AI agent installs it: 5 focused supply-chain tools.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `presend.pages.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/presendapp-presend-deps/mcp-deps.md), [page](https://verifymcp.io/servers/presendapp-presend-deps/mcp-deps)

## Channel facts

- Endpoint: `https://presend.pages.dev/mcp-deps`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 929 tokens (~185/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Presend dependency checks MCP server?

Presend dependency checks is a hosted endpoint at https://presend.pages.dev/mcp-deps, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http presendapp-presend-deps 'https://presend.pages.dev/mcp-deps'
```

### Cursor

```json
{
  "mcpServers": {
    "presendapp-presend-deps": {
      "url": "https://presend.pages.dev/mcp-deps"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "presendapp-presend-deps": {
      "type": "http",
      "url": "https://presend.pages.dev/mcp-deps"
    }
  }
}
```

### Codex

```toml
[mcp_servers.presendapp-presend-deps]
url = "https://presend.pages.dev/mcp-deps"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "presendapp-presend-deps": {
      "type": "remote",
      "url": "https://presend.pages.dev/mcp-deps",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add presendapp-presend-deps --url 'https://presend.pages.dev/mcp-deps' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  presendapp-presend-deps:
    url: "https://presend.pages.dev/mcp-deps"
```

### Netclaw

```json
{
  "McpServers": {
    "presendapp-presend-deps": {
      "Transport": "http",
      "Url": "https://presend.pages.dev/mcp-deps"
    }
  }
}
```

### Vellum

```bash
assistant mcp add presendapp-presend-deps -t streamable-http -u 'https://presend.pages.dev/mcp-deps'
```

### Other

```json
{
  "mcpServers": {
    "presendapp-presend-deps": {
      "type": "http",
      "url": "https://presend.pages.dev/mcp-deps"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-03 (score 69)

First indexed and scored.

## MCP tools (5)

### `maintainer_change_check` (~196 tokens)

Package maintainer change check

Publisher-change analysis is npm only. Also reports whether the package exists (found) and its age (first_published, package_age_days, new_package if first published less than 30 days ago), for npm and for PyPI; on PyPI only existence and age are available. Flags a previously unseen human publisher taking over a package after 180+ days of inactivity, within the last 365 days (the event-stream attack pattern). npm trusted publishing (verified OIDC identity, not just a bot-like account name), pre-release, and handovers to a publisher who already maintains another widely used package (100k+ weekly downloads) are reported but not flagged. Does not detect hijacked existing accounts; a heuristic for review, not proof.

Input parameters:

- `ecosystem` (string, required): npm (full analysis) or pypi (existence and age only).
- `package` (string, required): Package name, e.g. lodash

### `repo_health_check` (~121 tokens)

Repository health check

Maintenance signals for a GitHub repository given as owner/name: stars, forks, open issues, license, archived and fork flags, creation date and age, days since last push, topics. Use it to judge whether a dependency looks maintained or abandoned. For an npm or PyPI package whose repository you do not know, supply_chain_check resolves it from registry metadata and includes these signals. GitHub only; missing or private repositories return found: false.

Input parameters:

- `repo` (string, required): GitHub repository in owner/name format, e.g. lodash/lodash.

### `supply_chain_check` (~322 tokens)

Package supply-chain check

Call this before installing or adding a package (npm install, pip install, a new entry in a manifest), especially one whose name you recalled or that a model suggested. One-call risk check: combines vulnerability_check (OSV.dev), typosquat_check, maintainer_change_check (npm only) and repo_health_check (when the GitHub repo can be resolved) into one overall verdict. A package that does not exist on npm or PyPI gets overall_risk 'package_not_found': the name may be invented and should not be installed. A package first published less than 30 days ago gets the 'new_package' flag and overall_risk 'review_recommended': new packages are where invented and look-alike names get registered, so the name is worth confirming against the project's own documentation before installing (on PyPI the age is that of the oldest release still published; being new does not make a package malicious). Use the individual tools to investigate one signal. Vulnerabilities are checked for the given version, or the latest published one (version_checked, version_source). If a check could not run (rate limit, upstream error), it is listed in unavailable_checks and overall_risk is 'incomplete', never 'no_signals_found'.

Input parameters:

- `ecosystem` (string, required): Package ecosystem, e.g. npm. maintainer-change-check only runs for npm.
- `package` (string, required): Package name to check.
- `version` (string): Exact version to check for known vulnerabilities. Optional: defaults to the latest published version (npm and PyPI).

### `typosquat_check` (~147 tokens)

Package typosquat check

Call before installing a package whose name you typed or recalled. Checks whether an npm or PyPI package name is a near-miss of a well-known package (typosquatting), with an edit-distance threshold scaled to name length; names of 3 characters or fewer are not fuzzy-matched. Uses a curated list of popular names, so a clean result does not prove a package is safe. It does not check that the package exists: supply_chain_check does.

Input parameters:

- `ecosystem` (string, required): Package ecosystem, e.g. npm or PyPI.
- `package` (string, required): Package name to check for likely typosquatting of a well-known package in the given ecosystem.

### `vulnerability_check` (~155 tokens)

Package vulnerability check

Checks a package (optionally a specific version) against OSV.dev for known vulnerabilities: npm, PyPI, Go, crates.io, Maven, RubyGems, Packagist and NuGet. For npm and PyPI, a name that does not exist returns found: false and vulnerable: null, never a clean result. Use supply_chain_check for a combined verdict.

Input parameters:

- `ecosystem` (string, required): Package ecosystem, e.g. npm, PyPI, Go, crates.io, Maven, RubyGems, Packagist, or NuGet.
- `package` (string, required): Package name to check against OSV.dev for known CVEs.
- `version` (string): Omit to check all versions of the package.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/presendapp-presend-deps/mcp-deps#diagnostics

## Score history

- 2026-10-04: 70
- 2026-10-03: 69

## Common questions

### What is the Presend dependency checks MCP server?

Presend dependency checks is an MCP server listed in the public MCP registry as io.github.presendapp/presend-deps. Check an npm/PyPI package before an AI agent installs it: 5 focused supply-chain tools. This page covers its hosted endpoint (https://presend.pages.dev/mcp-deps).

### Is the Presend dependency checks MCP server safe to use?

Presend dependency checks scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Presend dependency checks MCP server expose?

Presend dependency checks exposes 5 tools: maintainer_change_check, repo_health_check, supply_chain_check, typosquat_check, vulnerability_check. Their descriptions and schemas cost roughly 941 tokens of context every time the server is loaded.

### Does the Presend dependency checks MCP server require authentication?

No. We connected to Presend dependency checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Presend dependency checks MCP server still maintained?

Presend dependency checks is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://presend.pages.dev/mcp-deps
- Repository: https://github.com/presendapp/presend-source
- Changelog RSS feed: https://verifymcp.io/servers/presendapp-presend-deps/mcp-deps.xml
- Changelog JSON feed: https://verifymcp.io/servers/presendapp-presend-deps/mcp-deps.json
- HTML version of this page: https://verifymcp.io/servers/presendapp-presend-deps/mcp-deps