io.github.MediaShareORG/yourimageshare
NPM · YOURIMAGESHARE-MCP
MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.
Available components
Last scanned (12 hours ago)
Scores higher than 62% of npm servers
Category Documents and Files
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 481 tokens (~160/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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
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.
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 −2
- Stability: pass → 0.83 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 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 Oct 26 −5
- Source repository: pass → fail ▼ security
- 3 Oct 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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 −3
- Stability: pass → 0.80 functional
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 23 Oct 2026 · Analysed npm/yourimageshare-mcp@1.0.6
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
delete_upload Delete an upload ~104
Permanently delete one of your YourImageShare uploads by `id` - irreversible, the file and its links stop working immediately. Get the `id` from upload_image's response right after uploading, or from list_uploads if you no longer have it. Errors (not found, already deleted, wrong owner) come back as a normal tool error.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The upload id to delete (the `id` field returned by upload_image/list_uploads). |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| id | string | yes | – |
No examples provided.
list_uploads List your uploads ~117
List your YourImageShare uploads, newest first, 50 per page - use this to find an upload's `id` (needed by `delete_upload`) when you only have its URL or remember it by content, since there's no lookup-by-URL endpoint. Each result includes the same three link fields `upload_image` returns, plus `title` and `created_at`. An out-of-range page number returns an empty `data` array, not an error.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number. Defaults to 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | object | yes | – |
No examples provided.
upload_image Upload an image or video ~260
Upload an image or video to YourImageShare and get back a shareable link. Accepts JPG, PNG, GIF, WEBP, AVIF, BMP, TIFF, HEIC/HEIF images and MP4, WEBM, AVI video, 100KB-200MB. Provide `path` for a file on disk this server can read, or `base64` + `filename` for in-memory content (e.g. no local filesystem access) - never both. Returns three different URLs for the same upload (see output fields): a raw storage link, a direct embeddable link, and a shareable page link - pick whichever fits where it's going. Errors (oversized/unsupported file, bad API key, rate limit) come back as a normal tool error, not a thrown exception.
| Name | Type | Req | Description |
|---|---|---|---|
| base64 | string | – | Base64-encoded file contents. Requires `filename`. |
| expiresIn | integer | – | Auto-delete after this many seconds (60 to 2,592,000 = 30 days). Omit for a permanent upload. |
| filename | string | – | Filename to use. Required with `base64`; inferred from `path` otherwise. |
| path | string | – | Local file path to upload. |
| Name | Type | Req | Description |
|---|---|---|---|
| direct | string | yes | The shareable page URL (title, description, comments, share buttons). Despite the field name, this is NOT a direct file link - use `src` for that. |
| expires_at | string|null | yes | ISO 8601 auto-delete timestamp, or null if the upload never expires. |
| id | string | yes | Unique identifier for this upload. Pass to delete_upload to remove it. |
| path | string | yes | Raw storage URL - the literal file, e.g. i.yourimageshare.com/xxx.webp. |
| src | string | yes | Direct/embeddable file URL - use this for <img>/<video> src attributes. |
| type | string | yes | – |
No examples provided.
How do I install the io.github.MediaShareORG/yourimageshare MCP server?
io.github.MediaShareORG/yourimageshare runs locally as an npm package, launched with npx -y yourimageshare-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 · yourimageshare-mcp
claude mcp add mediashareorg-yourimageshare -- npx -y yourimageshare-mcp
What is the io.github.MediaShareORG/yourimageshare MCP server?
io.github.MediaShareORG/yourimageshare is an MCP server listed in the public MCP registry as io.github.MediaShareORG/yourimageshare. MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents. This page covers its npm package (yourimageshare-mcp).
Is the io.github.MediaShareORG/yourimageshare MCP server safe to use?
io.github.MediaShareORG/yourimageshare scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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.MediaShareORG/yourimageshare MCP server expose?
io.github.MediaShareORG/yourimageshare exposes 3 tools: upload_image, list_uploads, delete_upload. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Is the io.github.MediaShareORG/yourimageshare MCP server still maintained?
io.github.MediaShareORG/yourimageshare is still listed as active in the MCP registry. We last reached this channel on 23 October 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.MediaShareORG/yourimageshare MCP server under?
io.github.MediaShareORG/yourimageshare declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.