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

sh.objekt/mcp-upload

NPM · @OBJEKT.SH/MCP-UPLOAD · SCANNED AUG 3

Public file storage for AI agents. Upload files and get a permalink back.

+30 this week 76 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to 0xLighthouse/objekt-mcp-upload). View diagnostics → Pass
  • License check failed: no license is declared. See how to fix → Fail
  • Actively maintained (last published 121 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 654 tokens (~109/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 Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @objekt.sh/mcp-upload

# add to Claude Code
claude mcp add sh-objekt-mcp-upload -- npx -y @objekt.sh/mcp-upload
# add to Codex CLI
codex mcp add sh-objekt-mcp-upload -- npx -y @objekt.sh/mcp-upload
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sh-objekt-mcp-upload": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@objekt.sh/mcp-upload"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sh-objekt-mcp-upload --command npx --arg -y --arg @objekt.sh/mcp-upload
# ~/.hermes/config.yaml
mcp_servers:
  sh-objekt-mcp-upload:
    command: "npx"
    args: ["-y", "@objekt.sh/mcp-upload"]
// mcp.json
{
  "mcpServers": {
    "sh-objekt-mcp-upload": {
      "command": "npx",
      "args": [
        "-y",
        "@objekt.sh/mcp-upload"
      ]
    }
  }
}
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.

  • 3 Aug 26 +4
    • Stability: unverified → 0.23 functional
  • 2 Aug 26 +67
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: 0xLighthouse/objekt-mcp-upload security
    • License: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Dependency health: unverified → partial functional
  • 1 Aug 26 −16
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +4
    • Malware scan: pass → unverified security
    • Tool coverage: unverified → 100 functional
  • 28 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/@objekt.sh/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
0xLighthouse/objekt-mcp-upload
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/0xLighthouse/objekt-mcp-upload/.github/workflows/publish.yml@refs/tags/[email protected]
Rekor log index:
1229118183
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:5625dc4ad31326a27a796fe200cb8057ca7715574ca46496ddf1988061baa6a037cd65c5c8c3b9bae71cd61fde112c7d405ed3dc2c378126526a54d28
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~488 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.

Tool Tokens
check_connection ~53

Test connectivity to api.objekt.sh. Use this to diagnose sandbox egress issues. If it fails, the user needs to add api.objekt.sh to their domain allowlist (Settings → Capabilities → Domain Allowlist).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_file ~45

Get a file from objekt.sh by name. Returns a link to the file without downloading the content.

NameTypeReqDescription
namestringyesFile name/key (e.g. 'photo.png')

No output schema declared.

No examples provided.

get_pricing ~19

Get current storage pricing and limits from objekt.sh.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_version ~19

Returns the installed version of the Objekt.sh MCP server.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

upload_file ~252

Upload a file to objekt.sh storage. Accepts a host file path OR base64/raw content. For files on the HOST filesystem (e.g. /Users/name/photo.png): use 'path' — reads from disk, fastest. For files you have in memory: use 'content' + 'content_type'. For files at CONTAINER paths (e.g. /mnt/user-data/): use the upload_from_sandbox tool instead.

NameTypeReqDescription
contentstringFile content — base64-encoded for binaries, raw UTF-8 for text. Use this when the file path is not accessible from the host filesystem.
content_typestringMIME type (required with content, e.g. 'image/png'). Auto-detected when using path.
encodingstringContent encoding. Default 'base64'. Use 'raw' for text types like SVG, HTML, CSS, JSON.
namestringFilename for the upload. Auto-detected from 'path'. Required when using 'content'.
pathstringAbsolute path to the file on the HOST filesystem (e.g. /Users/you/photo.png). Do NOT use container paths like /mnt/user-data/.

No output schema declared.

No examples provided.

upload_from_sandbox ~100

Upload a file from a sandbox/container path (e.g. /mnt/user-data/, /home/claude/) that the host cannot access. Reads the file and uploads it directly — single tool call, no shell commands needed.

NameTypeReqDescription
namestringCustom name for the uploaded file. Defaults to the filename.
sandbox_pathstringyesPath to the file inside the sandbox (e.g. /mnt/user-data/uploads/photo.png)

No output schema declared.

No examples provided.