Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Easysend-co/easysend

NPM · EASYSEND-MCP · SCANNED SEP 20

EasySend file sharing MCP server - upload, download and share files. No authentication required.

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 332 tokens (~55/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_file" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Easysend-co/easysend MCP server?

io.github.Easysend-co/easysend runs locally as an npm package, launched with npx -y easysend-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · easysend-mcp

# add to Claude Code
claude mcp add easysend-co-easysend -- npx -y easysend-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "easysend-co-easysend": {
      "command": "npx",
      "args": [
        "-y",
        "easysend-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "easysend-co-easysend": {
      "command": "npx",
      "args": [
        "-y",
        "easysend-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add easysend-co-easysend -- npx -y easysend-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "easysend-co-easysend": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "easysend-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add easysend-co-easysend --command npx --arg -y --arg easysend-mcp
# ~/.hermes/config.yaml
mcp_servers:
  easysend-co-easysend:
    command: "npx"
    args: ["-y", "easysend-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "easysend-co-easysend": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "easysend-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add easysend-co-easysend -t stdio -c npx -a -y easysend-mcp
// mcp.json
{
  "mcpServers": {
    "easysend-co-easysend": {
      "command": "npx",
      "args": [
        "-y",
        "easysend-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed npm/easysend-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~332 tokens

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 →

Tool Tokens
bundle_status ~39

Quick status check on an EasySend bundle - is it alive or expired, space remaining.

NameTypeReqDescription
short_codestringyesThe bundle code

No output schema declared.

No examples provided.

delete_file ~51

Delete a file from an EasySend bundle. Requires the upload_token returned during upload.

NameTypeReqDescription
file_idnumberyesThe file ID to delete
upload_tokenstringyesThe upload token for authorization

No output schema declared.

No examples provided.

download_bundle ~49

Download ALL files from an EasySend bundle to a local directory.

NameTypeReqDescription
save_dirstringDirectory to save files (default: current directory)
short_codestringyesThe bundle code

No output schema declared.

No examples provided.

download_file ~62

Download a single file from an EasySend bundle by file ID and save it to disk.

NameTypeReqDescription
file_idnumberyesThe file ID from bundle info
save_pathstringOptional path to save the file (default: current directory with original name)

No output schema declared.

No examples provided.

get_bundle ~64

Get information about an EasySend bundle - file list, sizes, download counts, expiry time.

NameTypeReqDescription
short_codestringyesThe bundle code from the share URL (e.g. "Ab3Kz" from easysend.co/Ab3Kz)

No output schema declared.

No examples provided.

upload_files ~67

Upload one or more files to EasySend and get a shareable link. No authentication required. Accepts any file type up to 1GB total.

NameTypeReqDescription
descriptionstringOptional note/description visible to recipients
filesarrayyesArray of absolute file paths to upload

No output schema declared.

No examples provided.

Common questions

What is the io.github.Easysend-co/easysend MCP server?

io.github.Easysend-co/easysend is an MCP server listed in the public MCP registry as io.github.Easysend-co/easysend. EasySend file sharing MCP server - upload, download and share files. No authentication required. This page covers its npm package (easysend-mcp).

Is the io.github.Easysend-co/easysend MCP server safe to use?

io.github.Easysend-co/easysend scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.Easysend-co/easysend MCP server expose?

io.github.Easysend-co/easysend exposes 6 tools: upload_files, get_bundle, download_file, download_bundle, delete_file, bundle_status. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.

Is the io.github.Easysend-co/easysend MCP server still maintained?

io.github.Easysend-co/easysend is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Easysend-co/easysend MCP server under?

io.github.Easysend-co/easysend declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.