Presend dependency checks
REMOTE · PRESEND.PAGES.DEV · SCANNED OCT 4
Check an npm/PyPI package before an AI agent installs it: 5 focused supply-chain tools.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · presend.pages.dev
claude mcp add --transport http presendapp-presend-deps 'https://presend.pages.dev/mcp-deps'
{
"mcpServers": {
"presendapp-presend-deps": {
"url": "https://presend.pages.dev/mcp-deps"
}
}
} {
"servers": {
"presendapp-presend-deps": {
"type": "http",
"url": "https://presend.pages.dev/mcp-deps"
}
}
} [mcp_servers.presendapp-presend-deps] url = "https://presend.pages.dev/mcp-deps"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"presendapp-presend-deps": {
"type": "remote",
"url": "https://presend.pages.dev/mcp-deps",
"enabled": true
}
}
} openclaw mcp add presendapp-presend-deps --url 'https://presend.pages.dev/mcp-deps' --transport streamable-http
mcp_servers:
presendapp-presend-deps:
url: "https://presend.pages.dev/mcp-deps" {
"McpServers": {
"presendapp-presend-deps": {
"Transport": "http",
"Url": "https://presend.pages.dev/mcp-deps"
}
}
} assistant mcp add presendapp-presend-deps -t streamable-http -u 'https://presend.pages.dev/mcp-deps'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 8 Oct 2026 · Probed https://presend.pages.dev/mcp-deps
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=presend.pages.dev | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c75807a7f16c8b81358d6a9d50c566f |
| SANs: presend.pages.dev, *.presend.pages.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of presend.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pages.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://presend.pages.dev/mcp-deps | Verified | 200 | |
| http (plaintext) | http://presend.pages.dev/mcp-deps | HTTPS enforced | 301 | https://presend.pages.dev/mcp-deps |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
maintainer_change_check Package maintainer change check ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | npm (full analysis) or pypi (existence and age only). |
| package | string | yes | Package name, e.g. lodash |
No output schema declared.
No examples provided.
repo_health_check Repository health check ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | GitHub repository in owner/name format, e.g. lodash/lodash. |
No output schema declared.
No examples provided.
supply_chain_check Package supply-chain check ~322
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem, e.g. npm. maintainer-change-check only runs for npm. |
| package | string | yes | Package name to check. |
| version | string | – | Exact version to check for known vulnerabilities. Optional: defaults to the latest published version (npm and PyPI). |
No output schema declared.
No examples provided.
typosquat_check Package typosquat check ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem, e.g. npm or PyPI. |
| package | string | yes | Package name to check for likely typosquatting of a well-known package in the given ecosystem. |
No output schema declared.
No examples provided.
vulnerability_check Package vulnerability check ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem, e.g. npm, PyPI, Go, crates.io, Maven, RubyGems, Packagist, or NuGet. |
| package | string | yes | Package name to check against OSV.dev for known CVEs. |
| version | string | – | Omit to check all versions of the package. |
No output schema declared.
No examples provided.
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.