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.img-src-io/mcp

NPM · @IMG-SRC/MCP-SERVER · SCANNED SEP 20

MCP server for img-src.io Image CDN - upload, transform, and deliver images through AI assistants

Available components

0 this week 83 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 Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 767 tokens (~95/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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_image" 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 8 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.img-src-io/mcp server?

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

npm · @img-src/mcp-server

# add to Claude Code
claude mcp add img-src-io-mcp -- npx -y @img-src/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "img-src-io-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@img-src/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "img-src-io-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@img-src/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add img-src-io-mcp -- npx -y @img-src/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "img-src-io-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@img-src/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add img-src-io-mcp --command npx --arg -y --arg @img-src/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  img-src-io-mcp:
    command: "npx"
    args: ["-y", "@img-src/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "img-src-io-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@img-src/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add img-src-io-mcp -t stdio -c npx -a -y @img-src/mcp-server
// mcp.json
{
  "mcpServers": {
    "img-src-io-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@img-src/mcp-server"
      ]
    }
  }
}
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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 14 Sept 26 +1

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

  • 10 Sept 26 +3
    • Source repository: unverified → pass security
    • Stability: pass → 0.80 functional
  • 9 Sept 26 −5
    • Provenance: pass → unverified security
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
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/@img-src/mcp-server@0.2.5

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 · 8 exposed · ~767 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
delete_image ~65

Delete an image by its ID. This permanently removes the image and all its paths from your account. The image will no longer be accessible via CDN URLs.

NameTypeReqDescription
idstringyesImage ID to delete (16-character hash prefix). This permanently removes the image and all its paths.

No output schema declared.

No examples provided.

get_cdn_url ~155

Generate a CDN URL for an image with optional transformations. Supports resizing, format conversion, and quality adjustment.

NameTypeReqDescription
filepathstringyesImage path without extension (e.g., 'blog/photo' for blog/photo.webp)
fitstringResize fit mode: cover (crop), contain (fit), fill (stretch), scale-down (shrink only)
formatstringOutput format (default: webp)
heightintegerResize height in pixels
qualityintegerImage quality 1-100 (default: 80)
usernamestringyesimg-src.io username (appears in CDN URL path)
widthintegerResize width in pixels

No output schema declared.

No examples provided.

get_image ~60

Get detailed metadata for a specific image by its ID. Returns full image information including dimensions, format, all associated paths, and CDN URLs.

NameTypeReqDescription
idstringyesImage ID (16-character hash prefix, e.g., 'abcdef1234567890')

No output schema declared.

No examples provided.

get_settings ~29

Get your img-src.io account settings. Returns username, plan, default image settings, and account statistics.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_usage ~35

Get current usage statistics for your img-src.io account. Shows uploads, storage, bandwidth, and API request usage against your plan limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_images ~100

List images in your img-src.io account. Supports pagination and folder browsing. Returns images and subfolders in the specified path.

NameTypeReqDescription
folderstringFolder path to filter images (e.g., 'blog/2024'). Omit to list root level.
limitintegerMax images to return (1-100, default: 50)
offsetintegerNumber of images to skip for pagination (default: 0)

No output schema declared.

No examples provided.

search_images ~94

Search for images by filename or path. Performs a fuzzy search across all your images. Returns matching images with their metadata and CDN URLs.

NameTypeReqDescription
limitintegerMax results to return (1-100, default: 20)
offsetintegerNumber of results to skip for pagination (default: 0)
querystringyesSearch term to match against filenames and paths (1-100 chars)

No output schema declared.

No examples provided.

upload_image ~229

Upload an image to img-src.io. IMPORTANT: Always prefer 'file_path' (absolute path like /Users/name/image.png) over base64 'data' to avoid context length limits. Use 'url' for web images. Only use 'data' as last resort for small images. Supports JPEG, PNG, WebP, GIF, AVIF, HEIC, and more. Max 5MB. Returns CDN URLs for the uploaded image.

NameTypeReqDescription
datastringBase64-encoded image data. AVOID: causes context length issues. Use file_path instead.
file_pathstringPREFERRED: Absolute path to local image file (e.g., /Users/name/photo.png). Use this instead of base64 data.
mimeTypestringMIME type (required only when using data, e.g., image/png)
target_pathstringOptional: Folder path to store the image (e.g., 'photos/2024'). Filename is determined from source.
urlstringURL of image to download and upload (for web images)

No output schema declared.

No examples provided.

Common questions

What is the io.github.img-src-io/mcp server?

io.github.img-src-io/mcp is listed in the public MCP registry as io.github.img-src-io/mcp. MCP server for img-src.io Image CDN - upload, transform, and deliver images through AI assistants. This page covers its npm package (@img-src/mcp-server).

Is the io.github.img-src-io/mcp server safe to use?

io.github.img-src-io/mcp scores 83 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.img-src-io/mcp server expose?

io.github.img-src-io/mcp exposes 8 tools: upload_image, list_images, search_images, get_image, delete_image, and 3 more. Their descriptions and schemas cost roughly 767 tokens of context every time the server is loaded.

Is the io.github.img-src-io/mcp server still maintained?

io.github.img-src-io/mcp 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.img-src-io/mcp server under?

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